Example project: one pallet, PO to bin
Prairie Supply Co. is fictional, and so is everything on this page. We invented one distributor and one pallet to show the scans, records and documents a real engagement produces.
Scope a project like this
Example (fictional). Prairie Supply Co. is fictional. The company, its people, systems, suppliers, quantities and documents on this page are invented to show how an engagement works. Nothing here describes a GenFrontier client or a result.
Prairie Supply Co. is an invented mid-size distributor in the Midwest with one main warehouse. Its ERP holds purchase orders and supplier records. Its WMS holds bin-level stock. Between the two, inbound trucks were tracked on a dock whiteboard and a shared spreadsheet. Buyers found out about short shipments when the paper packing list reached the office, often the next morning.
Prairie asked for inbound shipment tracking connected to the ERP and the WMS: know which trucks are on site, match each pallet to its purchase order, flag discrepancies to the buyer while the driver is still at the dock, and show the stock as available once it is in a bin. This page follows one pallet through the finished system, then shows an excerpt of the document each engagement stage produced.
The pallet we follow
| Field | Value |
|---|---|
| Purchase order | PO 4471, line 1 |
| Item | EX-20118 |
| Expected (from the supplier’s ASN) | 40 cases |
| Received | 39 cases |
| Pallet label | GS1 SSCC, sent in the supplier’s 856 ship notice |
| Put away to | Bin B-14 |
Six scans, from gate to bin
| Scan | Where | Who scans what | What the tracking layer records | What changes in the ERP or WMS |
|---|---|---|---|---|
| 1 | Gate | Guard scans the barcode on the bill of lading | Trailer arrived, linked to the ASN for PO 4471 | The expected receipt shows “On site” on the receiving screen |
| 2 | Dock door 3 | Receiver scans the gate ticket printed at check-in | Trailer at door 3, unloading started | Nothing posts yet; the dock board updates |
| 3 | Dock door 3 | Receiver scans the pallet’s SSCC label | Pallet matched to PO 4471 line 1: EX-20118, 40 cases expected | A receipt opens against PO 4471 in the WMS |
| 4 | Dock door 3 | Receiver scans one case label to confirm the item, then enters and confirms a count of 39 | Receipt confirmed; discrepancy event: expected 40, received 39 | WMS receives 39 cases; the ERP shows 39 received and 1 open on the line; the buyer is notified |
| 5 | Staging lane | Forklift driver scans the pallet to start the put-away task | Put-away started | WMS task moves to “In progress” |
| 6 | Bin B-14 | Driver scans the bin location label | Put-away confirmed at B-14 | WMS on-hand at B-14 rises by 39 cases, available to pick |
The buyer’s notice arrives while the trailer is still at the door. It shows the PO, item, expected and received quantities, the receiver and the time. Whether to keep the missing case on order, ask for a credit or cancel the balance is still the buyer’s decision. The software makes sure the decision is made the same day, with the facts on screen.
What the engagement produced
Stage 1: Walk the process
The walk covered the gate, three dock doors, the staging lane and the office. The notes recorded, among other things:
- The whiteboard listed expected trucks by supplier name, not PO number, so receivers searched the ERP for each delivery.
- Short and over counts were written on the paper packing list and keyed by an office clerk the next morning.
- Some suppliers sent 856 ship notices with SSCCs; others sent nothing, and their pallets arrived with no scannable label.
The process owner signed the current-state map and a first draft of the integration inventory.
Stage 2: Write the requirements
One of the requirements, with its acceptance test:
| ID | Requirement | Acceptance test |
|---|---|---|
| REQ-IN-07 | When the receiver confirms a case count that differs from the ASN quantity for a PO line, the system records a discrepancy event with the PO, line, item, expected quantity, received quantity, receiver and time, and notifies the buyer assigned to the PO within five minutes. | AT-IN-07. Setup: PO 4471 line 1, item EX-20118, ASN quantity 40 cases, buyer assigned. Steps: scan the pallet SSCC, scan one case label, enter 39 cases, confirm. Expected: a discrepancy event shows 40 expected and 39 received; the buyer receives a notice within five minutes; the ERP line shows 39 received and 1 open. |
Pallets without an ASN got their own requirements: the receiver selects the PO, and the system prints a GS1 SSCC label at the dock before the pallet moves.
Stage 3: Plan the project
An excerpt from the milestone table. The first increment covered one dock door and three suppliers that already sent ship notices.
| Milestone | What is done | Owner | Signed off by |
|---|---|---|---|
| M1 | Requirements specification signed | Operations manager | Operations manager, IT lead |
| M2 | 856 ship notices from three pilot suppliers loading in test | GenFrontier with Prairie’s EDI analyst | IT lead |
| M3 | Demo: scans 1 to 4 on test handhelds at dock door 3 | GenFrontier | Receiving lead |
| M4 | Demo: scans 5 and 6, with WMS and ERP postings | GenFrontier | Inventory lead, buyer |
| M5 | User acceptance testing passed | Prairie testers | Operations manager |
| M6 | Training delivered to all receiving, put-away and buying staff | GenFrontier | Receiving lead |
| M7 | Go-live at door 3, then doors 1 and 2 | Joint | Sponsor (go or no-go) |
Stage 4: Build and integrate
Two rows from the integration inventory, as they stood when the build started:
| ID | Interface | Direction | Trigger | Data | Method | Volume | Owner |
|---|---|---|---|---|---|---|---|
| INT-03 | Supplier ship notice | Supplier to Prairie’s EDI translator, then to the tracking layer | Supplier ships | X12 856: PO, SSCC, item, quantity, ship date | EDI through Prairie’s existing translator; file handed to the tracking layer | About 60 a day | Prairie EDI analyst |
| INT-05 | Receipt posting | Tracking layer to WMS | Receiver confirms a count | PO, line, item, quantity, SSCC, dock door | WMS API | One call per pallet | Prairie IT lead |
Stage 5: Test and cut over
One user acceptance test case, with its history:
| Field | Entry |
|---|---|
| Case | UAT-12: Short receipt on a pallet with an ASN |
| Tester | Second-shift receiver |
| Preconditions | Test PO 4471 line 1 open for 40 cases of EX-20118; ASN loaded; buyer assigned |
| Steps | Scan the pallet SSCC at door 3; scan one case label; enter 39 cases; confirm the count |
| Expected | Discrepancy event recorded; buyer notified within five minutes; ERP shows 39 received, 1 open |
| Run 1 | Fail. The notice went to a general inbox because the test PO had no buyer assigned. Test data corrected. |
| Run 2 | Pass |
Cutover started at door 3 only, with doors 1 and 2 on the old process for one more week. The rollback criterion was written down in advance: if receipts stopped posting to the WMS and could not be resent within the shift, receiving at door 3 would return to paper.
Stage 6: Document and onboard
An excerpt from the integration runbook:
Example (fictional). Runbook entry INT-05: a receipt has not posted to the WMS.
Symptom. The receiving screen shows “Posting pending” for more than 10 minutes.
- Open the interface monitor and filter on INT-05. Find the pallet by SSCC or PO.
- If the status is “Rejected: location locked”, the bin is in a cycle count. Wait for the count to close; the posting resends on its own. Do not rescan the pallet.
- If the status is “WMS unavailable”, postings are queued and resend when the WMS returns. Tell the receiving lead that stock will show late.
- If neither applies, record the SSCC and error text and escalate to Prairie’s IT on-call contact.
And the training plan:
| Role | Session | Length | Where | Materials |
|---|---|---|---|---|
| Receivers | Scanning an inbound pallet; short and over counts; pallets with no ASN | 60 minutes | On the dock with test handhelds | Quick card, SOP RCV-02 |
| Forklift drivers | Put-away scans and what to do when a bin is full | 30 minutes | Staging lane | Quick card, SOP PUT-01 |
| Buyers | Reading discrepancy notices and recording the decision | 45 minutes | Video call | User guide, section 4 |
| Receiving supervisor | Dock board, exception queue, reassigning tasks | 90 minutes | Office and dock | Supervisor guide |
| IT administrators | Interface monitor, runbook, user setup | 2 hours | Video call | Admin guide, integration runbook |
What this example leaves out
A real engagement produces more than these excerpts: the full process map, dozens of requirements, the whole integration inventory, the cutover plan and every guide. Real projects also differ in size, systems and timing, so nothing here is a promise about yours. If an inbound, outbound or inventory problem looks like Prairie’s, the engagement types page shows how to start, and the tracking milestone map is a free way to list your own scan points first.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.