# WMS rollout mis-pick records: advisor guide | SourceX

Canonical: https://refer.sourcex.si/guides/moment-wms-rollout-warehouse-automation-advisors
Last updated: 2026-10-20

Mis-picks are connected to corrections and the confirmed customer outcome only sometimes, and a WMS rollout is when you find out. A mis-pick usually leaves a trail across systems: a short-pick or wrong-item exception in the warehouse, a correction such as a reallocation or re-pick, a shipment, and later a customer claim, return reason and credit. Warehouse automation advisors can ask the owner whether those records still link by order or line. If they do and the company qualifies, the owner may want an introduction to SourceX, which licenses business data for AI training and evaluation.

## Are mis-picks connected to corrections and the confirmed customer outcome?

In many warehouses the pieces exist but sit in different systems, so the honest answer is often "partly". The rollout matters because data mapping is the one moment when someone checks whether order, line and exception keys carry across, or whether only open inventory and open orders move to the new WMS.

Here is why this specific chain is easy to overlook. Rollout teams map what the new system needs to run tomorrow: item masters, locations, open orders, on-hand stock. Exception history is not needed for go-live, so it tends to stay behind in the legacy database. Returns and credits often live in the ERP or order system, owned by finance or customer service rather than operations. Nobody on the project owns the join between them.

A worked record chain makes the question concrete. Illustrative: a 260-person regional distributor of industrial parts, one order line, field names simplified.

| Step | Record | Typical system | Key that links it to the next step |
|---|---|---|---|
| 1. Pick scan | Picker confirms location and quantity | Legacy WMS, mobile device log | Work ID and order line |
| 2. Exception | Short pick logged at the location | WMS work exceptions log | Work ID, location, item |
| 3. Correction | Stock reallocated to another location and re-picked | WMS work history | Same work ID, new location |
| 4. Shipment | Packed and shipped, sometimes still wrong | WMS and carrier manifest | Shipment ID and order line |
| 5. Customer claim | Customer reports wrong item or short quantity | Order system or helpdesk | Order number |
| 6. Outcome | Return order with reason code and a disposition such as credit or replace | ERP returns module | RMA number and original order line |

Not every WMS works the same way, so treat the columns as questions rather than assumptions. As one documented example, Microsoft's Dynamics 365 Supply Chain Management uses a Short pick work exception that can reallocate stock automatically, manually or both, and each short pick creates an entry in a work exceptions log. Its returns process records an RMA number, a return reason code and a disposition code on each line. Whether a given client's system keeps those links is exactly what your question tests.

Why would anyone outside the warehouse care? A connected chain shows an error, the decision taken to fix it and whether the fix worked for the customer. That cause, action and outcome pattern is a kind of multi-step operational record that rarely exists on the public web; whether a buyer wants a particular company's chain is known only after SourceX reviews it. The related page on [integration error-handling records](/data-types/integration-error-handling-records) covers a similar pattern on the systems side.

## How do you test the chain without touching the records?

Ask the question as written, then four metadata follow-ups, and stop. Every answer is a word, a range or a name; nothing needs to be exported, opened or screenshotted.

1. **What:** which of the six steps above does the company record, and in which system? Many will say steps 1 to 4 in the WMS and steps 5 and 6 in the ERP or helpdesk.
2. **Where it breaks:** which key would join a shipment to a later customer claim (order line, shipment ID, RMA reference), and does the rollout's data mapping keep that key in the archive?
3. **How much and how long:** years of exception and returns history, and a rough order-line volume per year across the sites covered.
4. **Who owns it:** who runs each system, and whether customer contracts limit reuse of order data. The company's counsel answers the second part.

Three answers are common. "Yes, the order line carries through" means a connected chain exists and the rollout decides whether it stays joinable. "Partly" usually means the warehouse half is linked but returns sit in a separate tool with only an order number, which is still a usable thread. "No" means the history was never linked or the legacy WMS keeps only current-state inventory; record that honestly and do not describe the archive as more than it is.

The same test works when the trigger is different. The [3PL WMS consolidation screen](/guides/3pl-acquisition-integration-wms) applies it across several acquired sites, and the [3PL bankruptcy guide](/guides/3pl-bankruptcy) covers the case where records are at risk because the business itself is winding down.

## Reward disclosure and owner permission

Raise the licensing option only with the owner, CEO or COO, after the chain question is answered, and disclose your interest before they decide. The project sponsor or warehouse manager can describe the records but usually cannot authorize a licensing discussion.

Say plainly that SourceX licenses approved business data directly from companies for AI training and evaluation, that you may receive a referral reward if a license completes, and that SourceX funds it separately so it never comes out of the company's payout. Then ask whether the owner wants an introduction or would rather leave it. Note the date and the answer.

If the owner opts in, the introduction names the record types and systems at metadata level and the authorized contact, and says that no records have been shared. If the owner declines, the question still helped the project: the archive decision is now on the record before cutover.

## Who owns warehouse exception records, and who can authorize a licensing discussion?

The operating company usually owns its WMS and ERP records, but rights to customer order data can be limited by customer contracts, so the company's own counsel answers that question, not you. The person who can open a licensing discussion is the CEO (in an owner-run company, usually the owner), not the project sponsor or warehouse manager.

| Question | Usually answered by | What stays unknown until SourceX reviews it |
|---|---|---|
| Which records exist and for how long | Operations lead or IT | Whether the records match current dataset demand |
| Whether customer contracts restrict reuse | The company's counsel | The outcome of SourceX's rights review |
| Who can authorize a discussion | CEO, often the owner | Any offer, its terms and timing |
| Company size and history | Owner or HR | Final eligibility confirmation |

Eligibility is set out on [who qualifies](/who-qualifies): 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.

On reward disclosure: the default reward is 25% of the Actual Supplier Payout, the amount SourceX actually pays the company, capped at $100,000 cumulatively per company across all agreements and renewals. Illustrative only: a $250,000 payout would mean a $62,500 reward. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards) explains each step. You sign the Channel Partner Agreement before submitting any introduction. Partners on other implementation projects can compare the [NetSuite project guide](/guides/how-erp-consultants-spot-referral-opportunities-during-netsuite-projects), and the [partner hub](/for) lists other roles.

## Go deeper on WMS rollouts

- [WMS rollout meeting agenda](/resources/wms-rollout-meeting-agenda): a minute-by-minute 15-minute owner conversation about pick-error recovery, ending in a clear opt-in.
- [WMS rollout archive context checklist](/resources/wms-rollout-archive-context-checklist): a data-mapping checklist of decommission, hosting, scope and archive-format facts to confirm before the old system retires.
- [WMS rollout introduction email](/resources/wms-rollout-introduction-email): a short email template for introducing the authorized contact to SourceX once the owner has opted in.

## Next step

> **Refer a company. Earn up to $100,000.** Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If your client's mis-pick chain survives into the archive and the owner opts in, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you send the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/tasks/set-up-short-picking-item-reallocation
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/work-exceptions-log
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/sales-marketing/sales-returns