Inbound shipment visibility means knowing which of seven milestones every open purchase order line has reached: released, acknowledged, ship notice received, picked up, in transit, booked and checked in at your dock, and received. You get there by asking suppliers for an acknowledgment and an advance ship notice (an X12 856 with an SSCC for each pallet, or the same data through a portal), getting the carrier, bill of lading and PRO number from the carrier or the supplier, and tying every event back to the PO number and line. The receiving dock then confirms the last milestone by scanning pallet labels against the ship notice.
Most of this data already exists somewhere. The supplier knows when it packed the order, the carrier knows when it picked up, and your yard knows when the trailer arrived. The work is getting each fact into one place, keyed to the PO, early enough to act on it. Until that happens, buyers phone suppliers, receivers learn what is on a truck when they open the doors, and short shipments surface the next morning when a paper packing list reaches the office.
This guide covers the milestone chain, the data to ask for, suppliers that will never send EDI, who books the freight, ASN receiving with SSCCs, supplier ASN compliance and where the timeline should live. Rules for acting on late or short shipments once they are visible belong to a separate question, covered in our guide to shipment exception management for B2B freight.
The milestone chain from purchase order to receipt
Seven milestones cover most domestic inbound freight. Each one has a single event that proves it, a system that holds it and a named person who acts when it is late.
| # | Milestone | Event that proves it | Typical message or source | Where it lives | Who acts when it is late |
|---|---|---|---|---|---|
| 1 | PO released | The buyer sends the PO to the supplier | X12 850 Purchase Order, supplier portal, or PDF by email | ERP purchase order | Buyer |
| 2 | PO acknowledged | The supplier confirms quantities, prices and ship date | X12 855 Purchase Order Acknowledgment, X12 865 for supplier-initiated changes, portal, or email reply | ERP PO confirmed date and quantity | Buyer |
| 3 | Ship notice received | The supplier lists what shipped: pallets, SSCCs, items, quantities, carrier | X12 856 Ship Notice/Manifest or a portal ship notice | ERP in-transit record or WMS expected receipt | Receiving lead |
| 4 | Picked up | The carrier leaves the supplier’s dock with the freight | X12 214 status, carrier API, or the signed bill of lading | Tracking layer or TMS | Logistics coordinator |
| 5 | In transit with an ETA | Location and estimated delivery updates | X12 214 status, carrier API, visibility platform feed | Tracking layer or TMS | Logistics coordinator |
| 6 | Booked and checked in | A dock appointment exists and the trailer checks in at the gate | Dock schedule, gate check-in scan | Yard or dock schedule | Receiving lead |
| 7 | Received | Pallets are scanned and counts confirmed against the ship notice | WMS receipt, optionally an X12 861 Receiving Advice/Acceptance Certificate back to the supplier | WMS, then the ERP PO receipt | Receiving lead, with the buyer for discrepancies |
The X12 names in this table are taken from the ASC X12 transaction set list. X12 describes the 856 as a set that “can be used to list the contents of a shipment of goods as well as additional information relating to the shipment,” including order information, packaging, marking, carrier information and the configuration of goods in the trailer (X12, 856 Ship Notice/Manifest). That last part is why the 856 sits at the center of inbound visibility: it is the only message in the chain that says what is physically on the truck.
Three timestamps on every milestone
A milestone is only useful if you can compare it with something. Store three times for each one:
- Planned: the date you expected the milestone when the PO was released or acknowledged. For pickup, that is the confirmed ship date.
- Estimated: the latest prediction, which changes as events arrive. A carrier’s estimated delivery is an estimate, not an actual.
- Actual: the time the event happened, as reported by whoever saw it.
Also store the time your system received each event. A ship notice that says the truck left on Monday but reached you on Wednesday is a late ship notice, even though the pickup itself was on time. The difference between event time and received time is how you measure supplier and carrier data quality later.
When a supplier skips a milestone
Not every PO passes through all seven steps, and the model should say so per supplier rather than show permanent gaps.
- Your own truck collects the order. Milestone 4 is your driver’s departure from the supplier, recorded by your dispatch or driver app.
- The supplier delivers on its own trucks. There is no carrier feed. Ask for the ship notice plus a driver ETA call or text at departure, and treat gate check-in as the first hard event after the ship notice.
- Parcel shipments. The parcel tracking number replaces the PRO number, and the ship notice should carry it.
You can draft this chain for your own operation, supplier by supplier, with the tracking milestone map. Its starting rows follow the same inbound sequence, and each row asks for a source, an owner, an expected time and an exception rule.
What data to ask suppliers for
Ask every supplier for the same short data set, whatever channel it uses: the PO number on every document, a confirmed ship date and quantity, and at shipment the carrier, the bill of lading and PRO numbers, and the pallets with their SSCCs and contents. The channel can differ by supplier; the fields should not.
| Data element | Why you need it | Where it travels in an X12 856 (release 4010) |
|---|---|---|
| PO number | The key every later event hangs on | PRF (Purchase Order Reference) segment at the order level |
| Ship notice number and purpose | Lets you tell an original notice from a replacement or a cancellation | BSN segment; purpose codes include 00 Original, 01 Cancellation and 05 Replace |
| Ship date and estimated delivery | Sets the planned and estimated times for milestones 4 to 6 | DTM (Date/Time Reference) segments |
| Carrier | Tells you who to ask for status | TD5 segment, with qualifier 2 for the Standard Carrier Alpha Code (SCAC) |
| Bill of lading number | The document the driver carries; ties carrier events to the ship notice | REF segment with qualifier BM (Bill of Lading Number) |
| PRO number | The carrier’s own shipment reference, used to query LTL status | REF segment with qualifier CN (Carrier’s Reference Number (PRO/Invoice)) |
| Pallet SSCCs | Lets a receiver scan one label and see what the pallet holds | MAN segment with qualifier GM (SSCC-18 and Application Identifier) at the tare or pack level |
| Item and quantity shipped | Matches the PO line and shows shorts before the truck arrives | LIN and SN1 (Item Detail (Shipment)) segments at the item level |
| Lot and expiry, when you track them | Needed for first-expired-first-out picking and recalls | Item level, per your implementation guide |
The segment and qualifier names above come from the X12 release 4010 code lists as reproduced in Stedi’s public EDI reference for the 856, a secondary source; your trading partner’s implementation guide is the document that binds. The 856 is also hierarchical: the HL segment’s level codes include S (Shipment), O (Order), T (Shipping Tare), P (Pack) and I (Item). Which levels a supplier sends decides whether you learn what is on each pallet or only what is on the truck. Our guide to choosing an EDI 856 hierarchy that matches your freight covers that choice in detail.
When the ship notice should arrive
GS1’s Logistic Label Guideline (Release 1.3, ratified July 2019) gives two timing rules that make a good contract clause. The despatch advice or ASN “should be sent upon staging / loading of the goods, in order to maximise the chance that the information matches the actual shipment,” and the receiver should receive and process it “before the goods arrive.” The first rule protects accuracy: a notice built from the order before the pallets are loaded describes the plan, not the truck. The second protects receiving: a notice that lands after check-in is no help at the door.
For short regional lanes, “before the goods arrive” can mean minutes. Write your own rule as a time before the dock appointment, not a time after shipment. For example, suppose you require the notice at least two hours before the appointment: a hypothetical supplier 45 minutes away must then send it at departure or earlier, while one three days away has plenty of room.
Put it in writing
The same GS1 guideline lists, among the receiver’s prerequisites, that “rejection of delivery (or otherwise) without Despatch Advice / ASN should be included in the contract.” Whether you would ever refuse a truck is a business decision. Writing the consequence down is what turns the ship notice from a favor into an obligation. A one-page inbound supplier guide usually covers:
- Which channel the supplier uses (EDI, portal or email template) and the contact for problems.
- The 856 implementation guide, or the portal fields that replace it.
- The pallet label specification, including where the SSCC label goes. Our article on SSCC pallet labels and GS1-128 layout covers numbering and print checks.
- The timing rule for acknowledgments and ship notices.
- How you will measure compliance and what happens at each score.
Supplier tiers: EDI, portal and email
Sort suppliers into three tiers by how they can send data, and collect the same milestones from each tier through a different channel. Waiting for every supplier to adopt EDI leaves your smallest and least reliable suppliers, often the ones that cause the most receiving work, permanently invisible.
| Tier 1: EDI | Tier 2: Portal | Tier 3: Email | |
|---|---|---|---|
| Who fits | Suppliers with an EDI translator or a provider already sending 855s and 856s to other customers | Suppliers who will key data into a web form but have no EDI | Small or occasional suppliers, and anyone who refuses the first two |
| Acknowledgment | X12 855, X12 865 for later changes | Supplier confirms each PO line on screen | Reply to a templated email; a buyer records the date and quantity |
| Ship notice | X12 856 with SSCCs at the tare or pack level | Supplier enters pallets and contents; the portal prints labels | Packing list attached to an email, keyed or checked by your staff |
| Pallet labels | Supplier prints GS1-128 labels with its own SSCCs | Portal-printed labels, or supplier labels with SSCCs entered on screen | Usually none; your dock labels pallets on arrival |
| Effort on your side | Mapping and testing per supplier, then monitoring | Building and supporting the portal, onboarding supplier users | Manual keying or checking for every shipment |
| Typical failure | Notice sent from the order instead of the loaded truck | Supplier stops logging in after the first month | No ship notice at all, so receipt is blind |
Rules for moving a supplier up a tier
Tier assignment should follow the receiving cost each supplier creates, not the supplier’s size. A practical scoring rule, all from your own receipt history:
- Receipt lines per month. A supplier that sends many lines a month repays mapping work faster than one that ships twice a year.
- Mixed pallets. Pallets carrying several items take longest to receive blind, so a supplier that ships mixed pallets moves up the list.
- Discrepancy history. A supplier with frequent short or over shipments benefits most from a notice that exposes the problem before the truck arrives.
- Lead time and distance. Long transit gives a ship notice more value, because you have time to act on it.
- Capability. Ask what the supplier already sends to its other customers. A supplier that emails you may already send 856s to someone else.
Making the email tier less manual
Email suppliers will stay email suppliers, so reduce the keying instead of fighting it. Send the PO with a reply template that lists each line, the ordered quantity and blank fields for the confirmed quantity and ship date. Ask for the carrier and PRO number in the same reply when the order ships. If you extract data from attached PDFs automatically, route each extraction to a person for confirmation before it updates the PO. A wrong confirmed date is worse than a missing one, because people trust it.
For pallets that arrive without labels, GS1’s guideline describes a pre-printed SSCC-only label that “can be applied anywhere in the supply chain (from when the pallet is produced to when it is received by a customer).” The guideline also says that if a logistic unit arrives without an SSCC, “the subsequent party in the supply chain may allocate the SSCC,” and that party can be the customer. Labeling unlabeled pallets at your own dock, with SSCCs from your own GS1 Company Prefix, gives every pallet in the building a scannable identity even when the supplier sends nothing.
Portal labels and whose numbers they use
A portal can print SSCC labels for suppliers that have no labeling capability. Decide up front whose GS1 Company Prefix those SSCCs use. The guideline says the SSCC “should be assigned by the company that is creating the logistic unit, using its own” prefix, so a supplier with its own prefix should use it. For suppliers without one, labels printed under your prefix from a reserved serial range keep every number unique and traceable to the portal shipment that created it.
Carrier data: who books the freight decides what you see
If you book the inbound freight, carrier status can come to you directly. If the supplier books it, you depend on the supplier to pass the carrier, bill of lading and PRO number so you can query the carrier yourself.
When you route the freight. You tender the load, by X12 204 Motor Carrier Load Tender or through your TMS, and the carrier accepts with an X12 990 Response to a Load Tender. Status messages arrive under your own arrangement with the carrier, by X12 214 Transportation Carrier Shipment Status Message or the carrier’s API. You know the carrier, the pickup appointment and the reference numbers because you created them.
When the supplier routes the freight. The carrier’s status feed goes to whoever arranged it with the carrier, and here that is the supplier, not you. Your tracking then starts from the ship notice: the SCAC tells you which carrier, and the PRO or bill of lading number is the query key for that carrier’s tracking API or website. If the ship notice lacks those references, you are back to phoning the supplier.
For most distributors the answer is a mix. A useful step is to list, for each of your top inbound suppliers, who pays and books the freight today, because that decides which feed you can build.
Which 214 status codes map to inbound milestones
A 214 carries a shipment status code. In the X12 release 4010 code list for element 1650 (Shipment Status Code), as reproduced in Stedi’s public reference, the codes that matter most for inbound tracking are:
| Code | X12 meaning | Inbound milestone it supports |
|---|---|---|
| X3 | Arrived at Pick-up Location | Carrier is at the supplier |
| AF | Carrier Departed Pick-up Location with Shipment | 4. Picked up |
| AG | Estimated Delivery | 5. ETA updated |
| SD | Shipment Delayed | 5. Exception input |
| X1 | Arrived at Delivery Location | 6. Carrier says it is at your site |
| D1 | Completed Unloading at Delivery Location | 7. Carrier says unloading finished |
| CD | Carrier Departed Delivery Location | Truck left your site |
Each carrier’s 214 implementation guide states which codes it actually sends and when, so check the guide rather than assuming the whole list. Treat the carrier’s X1 as the carrier’s claim and your gate check-in as yours. When the two disagree by hours, the gate scan is the record you can defend, and the gap is worth investigating.
Imported purchase orders add an ocean leg
For POs that arrive by ocean, extra milestones sit between pickup and your dock: cargo loaded at the foreign port, vessel departure, US port arrival, customs release and the drayage or rail move inland. The data owners are usually your freight forwarder and customs broker, not the supplier.
One milestone is fixed by regulation. Under 19 CFR 149.2, the importer security filing for vessel cargo must include the seller, buyer, importer of record number, consignee number, manufacturer or supplier, ship-to party, country of origin and commodity HTSUS number “no later than 24 hours before the cargo is laden aboard the vessel at the foreign port.” Container stuffing location and consolidator follow as early as possible, and no later than 24 hours before arrival in a US port. In practice that means your broker holds PO-level data before the ship sails. Ask for the filing date and the house bill of lading number as fields on the PO record, so the import leg starts with a known event instead of a supplier email.
Dock appointments and arrival at your gate
Tie every dock appointment to the PO numbers and ship notice it will deliver, and record your own gate check-in as the arrival event. Check-in is where the supplier’s ship notice, the carrier’s arrival status and your yard all meet, so it is the cheapest place to catch a mismatch.
A working appointment process for inbound freight:
- Request. The carrier or supplier requests a slot and gives the PO numbers, the ship notice number if one exists, and the pallet count.
- Validate. The scheduling screen checks that the POs are open and that a ship notice has arrived or is due. A request for a PO that is already fully received is a red flag.
- Confirm. The appointment number goes back to the requester. If the supplier sends the 856 after booking, ask it to carry the appointment number, which X12 provides as REF qualifier AO (Appointment Number).
- Check in. At the gate, the guard scans or keys the bill of lading, trailer number and seal number. The system links the trailer to the appointment, the ship notice and the POs.
- Assign a door. The dock board now shows expected pallets and SSCCs for that door before anyone opens the trailer.
Steps 4 and 5 are where inbound visibility pays at the dock: a receiver who sees the expected pallets and their contents can stage labor and space before the doors open.
How an ASN with SSCCs speeds receiving
With a ship notice that lists each pallet’s SSCC and contents, a receiver scans one label per pallet and the WMS already knows the items, quantities and PO. Without it, the receiver has to find the PO, then identify and count every item on every pallet. The speed comes from replacing item-level counting with pallet-level scanning, backed by audits.
GS1’s Logistic Label Guideline states the mechanism directly: “Scanning the SSCC barcode on each logistic unit allows the physical movement of units to be matched with the electronic business messages that refer to them,” which supports applications including “automated receiving.” The SSCC itself is 18 digits, shown on the label with GS1 Application Identifier (00): an extension digit, the GS1 Company Prefix, a serial reference and a check digit. The guideline calls the SSCC “the single mandatory element for all GS1 Logistic Labels.”
Three ways to receive a truck
| Method | What the receiver does | What the system does | When to use it |
|---|---|---|---|
| Blind receipt | Finds the PO, identifies each item, counts and keys each quantity | Records what the receiver entered | No ship notice, or the ship notice is known to be unreliable |
| ASN receipt without SSCCs | Opens the expected receipt from the ship notice, then identifies and counts each item | Compares counts with the notice and flags differences at once | Supplier sends an order-level or item-level notice but no pallet detail |
| ASN receipt with SSCCs | Scans each pallet label, opens only the pallets the audit rule selects | Receives the pallet contents from the notice and posts differences found in audits | Supplier sends pallet-level SSCCs and has a good accuracy record |
The guideline leaves the audit level to the trading partners: depending on the agreement, “the SSCC may be scanned and the goods accepted as complete as indicated in the Despatch Advice / ASN,” or the receiver may check contents, “particularly where the logistic unit contains multiple products.” It also says that when the SSCC is scanned “the received amount should be automatically added to the Warehouse system.”
Note the middle row. A ship notice without pallet detail helps you match and spot shorts early, but it does not remove much counting. The SSCC is what lets you stop counting.
Example (fictional). A distributor receives a 22-pallet truck from a supplier on PO EX-5520. Eighteen pallets carry a single item and four are mixed, with six items each, which makes 42 pallet-item lines. Counting each scan or keyed quantity as one dock entry:
- Blind receipt: 1 entry to find the PO, then an item scan and a keyed count for each of the 42 lines, for 85 entries.
- ASN without SSCCs: 1 scan to open the expected receipt, then the same 84 item scans and counts, for 85 entries. Differences are flagged at once, but the work barely changes.
- ASN with SSCCs, every mixed pallet opened: 22 SSCC scans, plus 48 entries to check the 24 lines on the four mixed pallets, for 70 entries.
- ASN with SSCCs, scan and accept with an audit of 1 pallet in 10: 22 SSCC scans, plus audits of one single-item pallet (2 entries) and one mixed pallet (12 entries), for 36 entries.
The supplier’s ASN accuracy score decides which of the last two rules applies.
A receiving procedure for ASN with SSCCs
- Load and validate the notice. When the 856 arrives, check that every PO is open, every item exists in your item master, quantities use a unit of measure you recognize, and no SSCC is already on file. Reject or hold failures and tell the supplier the same day.
- Link at check-in. The gate links the trailer to the notice, so the door shows expected SSCCs.
- Scan every pallet. Each SSCC scan pulls the pallet’s contents from the notice. An SSCC that is not on the notice puts the pallet on hold and opens a lookup by PO, not a blind receipt of the whole truck.
- Apply the audit rule. The system tells the receiver which pallets to open, based on the supplier’s score, mixed pallets and high-value items.
- Post differences as events. A short or over count posts against the PO line and notifies the buyer while the driver is still on site.
- Close the receipt. Optionally, send an X12 861 Receiving Advice/Acceptance Certificate to the supplier with the received quantities.
What breaks ASN receiving
- The notice describes the order, not the truck. GS1’s guideline says “only loaded pallets should be scanned” when building the notice, for exactly this reason.
- A replaced notice after arrival. Your WMS must apply a BSN purpose code 05 replacement cleanly or refuse it once receiving has started.
- Reused or duplicate SSCCs. Your validation in step 1 should catch them; a scan that matches an SSCC received last month is a supplier labeling error.
- Unreadable labels. Damage, wrap over the barcode or a label on the wrong face sends the pallet back to blind receipt.
- Unit-of-measure mismatches. The notice says 40 and the PO says 480 because one counts cases and the other counts eaches. Fix this in item master data before go-live, not at the door.
Measuring supplier ASN compliance
Measure four things per supplier per month: whether the ship notice arrived in time, whether its pallets and quantities matched what you received, whether the labels scanned and matched the notice, and whether the PO was acknowledged on time. Publish the formulas to suppliers before you publish their scores.
| Metric | Formula | Data you need |
|---|---|---|
| ASN timeliness | Receipts with a ship notice processed before your deadline ÷ all receipts from the supplier | Notice received time, appointment or check-in time |
| ASN accuracy | Receipts where every SSCC and quantity matched the notice ÷ receipts with a notice | Notice contents, audited or full receipt counts |
| SSCC match rate | Pallets whose scanned SSCC was on the notice ÷ pallets received | Pallet scans at the door |
| Label readability | Pallets that scanned without a relabel ÷ pallets received | Relabel or manual-entry events at the door |
| Acknowledgment timeliness | PO lines acknowledged within the agreed window ÷ PO lines sent | PO release time, acknowledgment time |
| Ship date reliability | Shipments picked up on the confirmed date ÷ shipments | Confirmed ship date, pickup event |
Counting rules to agree before the first scorecard
- The receiver’s count is the reference, after a recount. Before a discrepancy counts against a supplier, a second person recounts. Otherwise your receiving errors become the supplier’s score.
- Replacements after check-in count as late. A notice replaced after the truck arrived did not help the dock, whatever its content.
- Audited pallets only. In scan-and-accept mode, accuracy can only be measured on pallets you opened. Report the sample size next to the rate.
- Small samples get counts, not percentages. A supplier with three receipts in a month should see “2 of 3,” not “67 percent.”
- Separate missing from wrong. A missing notice and an inaccurate one need different fixes and different conversations.
Example (fictional). A monthly scorecard for three invented suppliers:
| Supplier | Receipts | ASN timeliness | ASN accuracy (audited pallets) | SSCC match rate | Receiving rule next month |
|---|---|---|---|---|---|
| EX-Supplier North | 46 | 45 of 46 | 31 of 31 | 412 of 414 | Scan and accept, audit 1 pallet in 10 |
| EX-Supplier River | 22 | 17 of 22 | 18 of 21 | 190 of 205 | Open all mixed pallets |
| EX-Supplier Plains | 9 | 3 of 9 | 4 of 9 | Not labeled | Blind receipt; move to portal tier |
The payoff for suppliers is the receiving rule in the last column. A supplier with a strong score gets its receipts posted sooner, so its invoices can be matched sooner, which gives it a reason to keep the score up. If you plan to charge back for missing or wrong notices, the charge, its trigger and the dispute process belong in the supplier agreement.
Where the inbound timeline should live
Keep the PO and its confirmed dates in the ERP, the expected receipt and pallet detail in the WMS, and the event history in whichever system you choose as the tracking layer. Then link all three with the PO number, the ship notice number and the SSCCs.
Most ERPs already have an object for goods between the supplier and your dock. In Oracle NetSuite, an inbound shipment record groups PO lines from one or more purchase orders and holds fields such as expected shipping date, expected delivery date, bill of lading and vessel number, and items can be received from it. In Microsoft Dynamics 365 Supply Chain Management, the inbound load “represents a vendor shipment of one or more orders,” can be created from the vendor’s advance shipment notice, and “lets the logistics coordinator track the load’s progress from the vendor.”
These objects hold the plan and a current status well. Before relying on one as your whole timeline, check whether it can store a time-stamped history of every carrier event with both event time and received time, or only the latest status and a few dates. If it only holds the latest status, you need a separate tracking layer that keeps the history and writes the key dates back.
Wherever the history lives, it needs a few rules:
- Keep the event time and the received time for every event.
- Never let an older event overwrite a later milestone; events arrive late, twice and out of order.
- Keep a mapping table from each carrier’s and supplier’s status codes to your seven milestones.
- Flag conflicts, such as a delivery event with no gate check-in, instead of guessing.
The integration inventory worksheet is a quick way to list the interfaces this needs: POs to suppliers, notices into the WMS, carrier status into the tracking layer and receipts back to the ERP. Building those interfaces is the core of ERP, WMS and EDI integration work, and the milestone model on top of them is what shipment tracking software built around your systems provides.
A rollout order for bringing suppliers on
Start with the receiving dock and the few suppliers that create the most receiving work, prove the chain on them, then extend tier by tier. In our engagements we start by walking the dock and writing the requirements before any supplier is asked to change anything, because the supplier guide is only as good as the receiving process it describes.
- Pull 90 days of receipts by supplier. Count receipts, receipt lines, mixed pallets and discrepancies per supplier. This ranking is your onboarding order.
- Record who books the freight for each of the top suppliers, and which carriers carry it.
- Write the inbound supplier guide: channel, 856 implementation guide or portal fields, label specification, timing rule and scorecard formulas.
- Pick two or three pilot suppliers that already send 856s to other customers. They need the least change.
- Test with real paper. Exchange test notices, then have the supplier ship sample labels and scan them at your own dock with your own scanners before the first live truck.
- Run in parallel. For the first few weeks, receive pilot trucks against the notice and also count them fully. Compare the two before you switch to scan and accept.
- Turn on the scorecard once each supplier has enough receipts for the counts to mean something.
- Add the portal and email tiers next, starting with the suppliers ranked highest in step 1.
- Train each role on its milestone: buyers on acknowledgments and discrepancy notices, receivers on SSCC scanning and holds, coordinators on carrier status.
The fictional example project, which follows one inbound pallet from PO to bin, shows what the requirements, test cases and runbook for this kind of rollout look like on paper.
What to do next
Inbound visibility starts with a list, not a platform. Before choosing any software, work through this checklist with purchasing, receiving and whoever runs your EDI:
- Write the seven milestones for your operation, with the event, source, system and owner for each. The tracking milestone map gives you a starting table.
- Rank suppliers by receiving work over the last 90 days and assign each to the EDI, portal or email tier.
- For the top suppliers, record who books the freight and whether the ship notice carries the SCAC, bill of lading and PRO number.
- Decide your ship notice deadline as a time before the dock appointment.
- Check that your WMS can receive by SSCC, hold unknown pallets and handle replaced notices.
- Confirm where the event history will live and that it keeps event time and received time.
- Draft the supplier scorecard formulas and the counting rules, and share them before the first score.
- Label unlabeled pallets at your dock with your own SSCCs so every pallet in the building scans.
If the list shows gaps you would rather scope with someone who has written these requirements before, you can describe your inbound process to us and we will start from the milestones you already have.
