# Store transfer discrepancies: a system map | SourceX

Canonical: https://refer.sourcex.si/guides/store-transfer-discrepancies-records-across-systems
Last updated: 2026-10-19

Reconstructing a store transfer discrepancy takes four joins: the transfer order number, the license plate number (LPN) on each shipping unit, the item and quantity on each line, and timestamps on both sides. The warehouse system holds the first half of the story, the store POS the second half, and the inventory adjustment and case note sit wherever inventory control works. The transfer order number pairs a shipment with its intended receipt; only an LPN can follow stock that went somewhere else.

This system map belongs to the [store transfer discrepancies hub](/guides/workflow-store-transfer-discrepancies), which traces a partial shipment posted as complete. This page shows which system holds each record and which key joins them.

## Six systems on the map, and who runs each

A multi-store retailer usually spreads one transfer over six places. Each row is one node.

| System | Record it holds | Linking key it shares | Usual owner |
|---|---|---|---|
| ERP or merchandising system | Transfer order header and lines, quantities | Transfer order number, item, line | Merchandise planning or replenishment |
| Warehouse management system | Pick and pack scans by LPN or unit, user, time | LPN, transfer order number | Distribution center manager |
| ERP shipment posting | Posted shipped quantity, user, time | Transfer order number, posting time | Distribution center, ERP administrator |
| Store register or receiving app | Received quantity per line, receiving associate, time | Transfer order number, LPN if scanned | Store systems or retail operations |
| Variance case tracker or mailbox | Investigation notes, decisions, follow-up | Transfer order number typed into the case | Inventory control |
| ERP inventory journal | Adjustment quantity, reason code, approver | Item, location, reason code | Finance controller |

The ERP and warehouse nodes are usually the best keyed. The case tracker is the weak node: it holds the reasoning, but its key is whatever someone typed.

## The joins and the gap each leaves when missing

| Key | Written at the origin | Written at the destination | Without it |
|---|---|---|---|
| Transfer order number | Header and lines in the ERP | Inbound document at the store | Booking and dispatch never pair up |
| LPN | Pack scan in the warehouse | Back-door scan at the store | Stock that lands at the wrong store stays orphaned |
| Line quantity | Posted shipped units | Booked units | Nobody can say which side miscounted |
| Timestamp | Pack scan and posting clock | Booking clock, case open and close | The sequence of events is guesswork |
| Cause | Rarely captured at dispatch | Short flag, adjustment code | Clerical slip and shrink look identical |

Each platform creates a slightly different paper trail, so confirm the record pairs with the company. Two documented examples show why. Microsoft's Dynamics 365 Commerce documentation says a store's POS can only book an inbound line once the shipping site has posted it, and refuses a booked quantity above the posted one; stores that ship from POS may close out a remainder at dispatch where underdelivery is permitted on the line. Oracle NetSuite pairs an item fulfillment with an item receipt entered against it. Either way, the comparison that reveals a shortfall is posted-versus-booked, not ordered-versus-booked.

That booking rule shapes one case type above all: a box dropped at the wrong store. The wrong store has nothing posted to book against, so its register has no clean way to take the stock in on that transfer. What it does instead, a found-stock adjustment, a phone call or nothing, is exactly what the map needs to show.

## One case joined end to end (Illustrative)

Illustrative and fictional: a 260-person home goods retailer with one distribution center and 22 stores. Identifiers are invented.

| Step | System | Record | Key carried forward |
|---|---|---|---|
| 1 | ERP | Transfer order TO-30418 to store A: 6 boxes of table lamps, 72 units | TO-30418 |
| 2 | Warehouse system | 6 boxes packed and labeled LPN-1 to LPN-6, loaded on a two-stop truck | LPNs, TO-30418 |
| 3 | ERP | Shipment posted for 72 units at 06:40 | TO-30418, posting time |
| 4 | Store A register | 60 units received; 12 short, short-receipt flag set | TO-30418, received quantity |
| 5 | Store B | Unexpected box LPN-4 scanned at the back door; no open transfer to receive against; manager emails inventory control | LPN-4 |
| 6 | Case tracker | Analyst opens a case citing TO-30418, matches LPN-4 from the pack scans to store B's email | TO-30418, LPN-4 |
| 7 | ERP journal | Inventory manager approves a 12-unit move from store B to store A, reason code "misrouted box" | Reason code, approver |
| 8 | Weekly report | Both stores show zero variance for the lamp item | Item, locations |

The order number joins steps 1, 3, 4 and 6. Only the LPN connects step 5: without it, store A shows an unexplained shortage and store B shows unexplained found stock, and a later reader would see two adjustments with no link between them. The case note in step 6 is where the decision lives.

## Where joins usually fail

- **No LPN labels.** Some warehouses scan only at line level. Then a misrouted box can be matched only by item and timing, which is weaker.
- **Case notes in email.** If inventory control works variances in a shared mailbox, the case exists but its key is free text.
- **Reason codes changed over time.** An adjustment from five years ago is unreadable without the code list in use then.
- **Closed stores.** Receipts held only on a closed store's register may never have been posted centrally; the [preservation timeline](/guides/preserve-store-transfer-discrepancies-records) covers that.

## Map questions for the inventory operations head

1. Which systems hold transfer orders, warehouse scans, postings, store receipts, cases and adjustments, and from which year?
2. Are LPNs scanned at both pack and receipt?
3. Where are variances investigated: a tracker, the ERP or email?
4. Do adjustments carry reason codes and an approver, and has the code list changed?
5. Roughly how many transfers a year, and what share end with a variance, from an existing report?
6. Who administers each system?

Put the answers in the [store transfer referral brief](/resources/store-transfer-discrepancies-referral-brief-template); who can approve a licensing discussion is covered in [who can license store transfer discrepancy records](/questions/who-can-license-store-transfer-discrepancies-records). The [systems directory](/systems) covers export questions by platform, the [general ledger reconciliation resource](/resources/mcp/mcp-general-ledger-reconciliation) shows the finance side of matching records, and [wholesale distribution](/industries/wholesale-distribution-data-monetization) and [inventory and fulfillment data](/data-types/inventory-and-fulfillment) give related context.

The company needs 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. Partners sign the Channel Partner Agreement before submitting introductions and never handle scans, receipts or exports. Whether employee IDs in scan logs limit licensing, and whether any buyer wants the history, stay unknown until SourceX reviews it with the company.

## 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 the inventory operations head confirms that transfer orders, LPN scans and adjustments can be lined up for most variances, [register as a partner](/register), check the retailer on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- https://learn.microsoft.com/en-us/dynamics365/commerce/pos-inbound-inventory-operation
- https://learn.microsoft.com/en-us/dynamics365/commerce/pos-outbound-inventory-operation
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2312912.html
- https://refer.sourcex.si/terms