Target Stores EDI Tour: 850 In, 856 and 810 Out, NetSuite in Sync
A Target Stores EDI order, start to finish, on real screens from a live InfiPlex account: the 850 lands as a normal order with its ship window and terms intact, NetSuite fulfills it, and InfiPlex sends the 856 with tracking and the 810 invoice back to Target Stores automatically. 850 in to 810 out in 47 minutes, in the timestamps. No signup, full written version below.
Eleven screens, one Target Stores 850 through to the 810
Click anywhere on the screen to advance. Every image is an unedited capture, including the shop log receipts for every EDI document and NetSuite call.
850 in, 856 and 810 out, NetSuite in sync. Nobody keyed in an EDI document.
Retailer compliance and ERP sync, running as one automatic flow.
Click anywhere to continue →
Every step, in writing
The same eleven screens as the walkthrough above, with what's actually happening on each one.
1. The Target Stores 850 lands as a normal order
Order 104391 arrives from Target Stores, an EDI 850 purchase order for 30 units of Example Product 1 at $378.00, pulled automatically with the ship-to, the requested routing (USE VRS/ShipIQ), and totals filled in. It sits in the same queue as every marketplace order, no EDI portal, no re-keying.
2. The EDI details and NetSuite IDs ride along
Everything the 850 carried is on the order: the ship window (August 27 to September 1), the ship-to store, and the invoice terms codes Target Stores expects echoed back on the 810. Below them, the NetSuite IDs, including the sales order this becomes, 16646894. One order record, both systems' language.
3. InfiPlex pushes the order into NetSuite
Two minutes after the 850 landed, the shop log reads "NetSuite Push Order: Successful," with the exact payload sent: order number, source, date. NetSuite now owns fulfillment, and InfiPlex logged the receipt.
4. The shipment comes back from NetSuite
Once NetSuite fulfills the order, the package appears on the InfiPlex order automatically: tracking 1Z111111112222, UPS Ground, all 30 units shipped. Nobody copied a tracking number between systems.
5. The log shows InfiPlex polling until the fulfillment exists
This is the receipt for step 4. At 9:33 am InfiPlex asked NetSuite for the shipment and got "found_shipment": false, it wasn't fulfilled yet. At 9:48 am the same call returned "found_shipment": true, and the tracking flowed in. InfiPlex keeps checking until NetSuite has actually shipped it, and the log shows every attempt.
6. The 856 goes to Target Stores with the tracking
Nine minutes after the shipment came back, the log reads "Target Stores Create Parcel for Tracking: Successful," carrying tracking 1Z111111112222. That's the advance ship notice on its way, on time, inside the ship window from step 2.
7. The 810 invoice builds itself from the order
Invoice 104391, dated the same morning, totaling $378.00, generated from the order with the terms Target Stores sent on the 850. Draft or closed-and-ready-to-send, your call, and every field is editable before it goes.
8. Line items and shipment details, tied together
The invoice carries the line detail, 30 units at $12.60, and the Target Stores tab ties it to the physical shipment: the same UPS tracking number and the exact ship date. When Target Stores matches the 810 against the 856, these agree, because they came from the same record.
9. The 810 goes out, and there's a receipt
"Target Stores Create Parcel for Invoice: Successful," invoice 1122 against order 104391. The 850 landed at 9:21 am, the 810 went out at 10:08 am. Forty-seven minutes, order to invoice, with every document logged.
10. Every warehouse, one running total
The 30 units came out of Main Warehouse (Midwest), now at 64, alongside Secondary Warehouse (West) at 44, Third Warehouse (East) at 12, and Canada at 0, one total of 120 wherever it's asked. EDI orders draw from the same inventory as every other channel.
11. Every deduction has a paper trail
The per-SKU log shows this order taking 30 units, right alongside every other order and manual adjustment, each with a date, quantity, and reason. When a warehouse count looks off, you read the trail instead of guessing which order did it.
Retailer EDI and NetSuite FAQ
Do I need separate EDI software to sell to Target Stores?
No. The 850 lands in InfiPlex as a normal order, as shown in step 1, with the ship window, ship-to store, and invoice terms attached. The 856 with tracking and the 810 invoice go back out from the same order record, and every document has a shop log receipt. There's no separate EDI portal to babysit and nothing to re-key.
How does the NetSuite side of this work?
InfiPlex pushes the order into NetSuite as a sales order, then polls until the fulfillment exists, step 5 shows the actual polling with "found_shipment" false and then true. When NetSuite ships it, the tracking flows back into InfiPlex automatically and drives the 856. NetSuite stays the system of record for fulfillment; InfiPlex handles the retailer compliance around it. More detail on the NetSuite integration overview.
What keeps the 856 and 810 consistent with each other?
They come from the same order record. The invoice's Target Stores tab carries the exact tracking number and ship date from the shipment, step 8, so when Target Stores matches the invoice against the ship notice, they agree. The invoice terms echoed on the 810 are the ones the 850 delivered, stored on the order from the moment it landed.
What does this cost and how long does setup take?
InfiPlex plans start at $49.99/month, and pricing is public on the pricing page, no sales call required to see it. Target Stores is one of 130+ channels and platforms in the integrations directory, and the product tour hub has live walkthroughs for Amazon, AliExpress, TikTok Shop, Temu, and Walmart if you want to watch other flows. The free demo runs InfiPlex against your actual channels, retailers, and ERP.
Want your retailer EDI running like this?
Plans start at $49.99/month. Watch it on your own retailers and ERP with a free demo.
