Supplier onboarding rarely fails on the commercial side. The contract gets signed, the parts get approved, and then the first shipment arrives at the plant and gets rejected because the label does not survive a plausibility check, or the despatch advice references a cumulative quantity the customer's system disagrees with. What went wrong was sequencing. Four workstreams — message setup, label approval, packaging approval and part approval — run in parallel from the day the business is awarded, owned by four different teams, against four different clocks, and the first shipment exposes whichever one finished last. Trading partner onboarding is commonly quoted as taking anywhere from a few weeks to several months depending on the customer's mapping requirements and how many message types are involved, which is a wide enough range that guessing is not a plan. Request the integration datasheet to see the sequence mapped against a first-shipment date.
Supplier Logistics Onboarding and Ramp
The message set to confirm before anyone starts mapping, the label standard your customer will actually validate against, packaging and part approval running on their own clocks, and a first-ninety-days sequence built backwards from the shipment date.
Confirm the Message Set Before Anyone Maps Anything
The most common wasted fortnight in onboarding is mapping a message the customer does not use, or discovering one they do that nobody scoped.
| Message | What it carries | Onboarding note |
|---|---|---|
| Delivery schedule VDA 4905 · DELFOR · ANSI 830 |
Expected demand over coming days, weeks or months — customer and supplier part numbers, plant, delivery location, quantities, dates, cumulative quantity and the scheduling agreement reference | Establishes the cumulative figure that everything downstream reconciles against |
| Just-in-time call-off VDA 4915 |
Short-horizon delivery calls against the schedule, in sequence-driven supply | Only where the programme runs JIT or JIS — confirm before scoping |
| Despatch advice VDA 4913 or 4987 · DESADV · ANSI 856 |
What is on the truck, how it is packed, and when it arrives | The most rejection-prone message. Must survive the customer's plausibility checks, not merely validate as syntax |
| Receiving advice RECADV |
Discrepancies between what was advised and what actually arrived | Agree during onboarding, not after the first mismatch — it is how corrections reach you |
| Invoice VDA 4938 · INVOIC · ANSI 810 |
The billing document, matched against schedule and despatch advice | Fails downstream when the despatch advice is missing or mismatched |
| Transport label VDA 4902 global transport label |
The physical identifier the receiving dock scans | Has to be generated from the same source as the despatch advice, or the two will disagree |
Labels Fail on Rules, Not on Format
A label can be perfectly formed against the standard and still be rejected. Four variables decide it, and all four are customer-specific.
The Cumulative Quantity Trap
Uniquely automotive, absent from most enterprise systems by default, and the reason new suppliers end up reconciling in spreadsheets within their first quarter.
Test the Failures, Not the Happy Path
A test cycle that only proves valid files pass has proved almost nothing. Published guidance names eight scenarios worth covering.
Most onboarding programmes track them as four separate checklists owned by four teams, which means nobody can answer that question until something slips. Bring a live onboarding to a 30-minute session and we'll map all four against the first-shipment date in Fleet Rabbit — message set, label approval, packaging approval and part approval on one timeline, with the dependencies visible.
Packaging Is Its Own Approval, With Its Own Lead Time
Frequently treated as a detail of the logistics agreement, and frequently the item that delays a launch.
Trial Shipments and Part Approval
Running alongside the logistics setup on a separate clock, with its own gating requirements.
The First Ninety Days
Sequenced backwards from the first shipment. The right-hand column is the one to argue about in the kick-off meeting.
| Phase | Logistics workstream | Quality workstream | If it slips |
|---|---|---|---|
| Days 1–15 | Confirm the required message set and portal arrangements. Establish connection method and identify the customer's implementation guideline | Kick off part approval planning and confirm the documentation package required | Everything downstream moves, since mapping cannot start against an unconfirmed message set |
| Days 15–40 | Message mapping and label specification against the customer's rules — dock codes, pack quantities, mixed and master label handling | Container specification submitted for approval and packaging procured | Trial shipment cannot be packed or labelled correctly |
| Days 40–65 | Test cycle covering revisions, duplicates, partials and mixed pallets — not only valid files. Verify cumulative reconciliation | Run-at-rate study, then initial part approval submission | Failures surface in live production instead of in test, at chargeback rates |
| Days 65–80 | Trial shipment with real labels, real containers and a live despatch advice | Approval feedback addressed; pre-approval documentation prepared if shipping early | First production shipment becomes the trial, with the plant waiting |
| Days 80–90 | Ramp with daily monitoring of rejections and discrepancy advices; agree the escalation route | Approval closed out and traceability chain verified from label to raw material | Early-life errors repeat unnoticed and become the baseline performance rating |
Where New Suppliers Actually Lose Time
Five recurring causes. None of them is the technical mapping work everyone budgets for.
Frequently Asked Questions
Published guidance puts trading partner onboarding at anywhere from a few weeks to several months, driven by the customer's specific mapping requirements and how many message types are in scope. The wide range is the point — the variable is not your technical capability but how many messages, how customer-specific the label rules are, and whether packaging and part approval run in parallel or sequentially. Confirm all four scopes before committing to a date.
Typically a delivery schedule, a despatch advice and an invoice at minimum, with a just-in-time call-off where the programme is sequence-driven and a receiving advice for discrepancy reporting. In European automotive these appear as VDA formats — 4905 for schedules, 4915 for JIT calls, 4913 or 4987 for despatch advice, 4938 for invoices — alongside the EDIFACT and ANSI equivalents elsewhere. The critical point is that not every customer uses every message, so the required set must be confirmed during onboarding rather than assumed.
Because rejection usually comes from customer-specific rules rather than from format. Variances in dock codes, pack quantities, mixed and master label handling, and shipping confirmation logic all cause failures the standard itself does not describe. The consequence is rejection, relabelling or chargebacks rather than a request to resend. Generate the label and the despatch advice from the same source, since two systems describing the same goods will eventually disagree.
Automotive scheduling runs on cumulative running totals rather than discrete orders, and both parties must agree on the figure. Standard enterprise systems frequently lack the cumulative reconciliation, rollback logic and model-year tracking required — so when customer and supplier totals drift apart, teams end up reconciling in spreadsheets, which slows shipping and undermines the next requirement calculation. Test this during onboarding, because discovering it in month four means discovering it in live production.
Eight scenarios: valid files, missing mappings, duplicate messages, forecast revisions, quantity changes, partial deliveries, mixed pallets and invoice reconciliation. Most onboarding cycles test the first and skip the rest — yet forecast revisions and mixed pallets are the two most frequent live events. A test cycle that only proves valid files pass has proved almost nothing about how the integration behaves on a normal Tuesday.
Manufacturers commonly require a run-at-rate study first, verifying the actual production process can meet programme volumes at an acceptable first-time pass rate. Shipments made before approval typically require a full dimensional layout, with material certification on prototype product sent ahead. Traceability expectations run from the ship date or lot number on the packaging label back to raw material, process and dimensional records — which makes the label the entry point to the whole quality chain.
With genuine recovery time behind it — around day 65 to 80 of a ninety-day ramp rather than the week before launch. Use real containers, real labels and a live despatch advice, because a trial that substitutes any of those is not testing the thing that fails. A trial shipment with no time to fix what it finds is simply a first shipment with optimistic labelling. Start free with three assets and hold the sequence on one record.
