# Store transfer discrepancy records | SourceX

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

The records that explain a store transfer discrepancy are the transfer order, the dispatch scans at the shipping site, the shipment posting, the store receipt, the variance case or ticket where someone investigated, and the inventory adjustment with its reason code and approver. Together they show the gap, the decision and the closed variance. A retail ERP partner should confirm these exist at metadata level, then introduce the inventory operations head.

## What turns a store transfer into an exception?

A store transfer moves stock from a distribution center or another store to a store. It becomes an exception when the quantities disagree: what was ordered, what was scanned out, what was posted as shipped and what the store received are not the same number. The work is finding which number is wrong, deciding what happened to the difference and correcting stock in both locations.

The software rarely settles this alone. In Microsoft Dynamics 365 Commerce, transfer order lines become available to receive in the store's POS once the outbound warehouse posts them as shipped, and over-receiving is not permitted for transfer orders, so a store cannot record more than was posted. Stores that ship from POS can close or cancel remaining quantities during shipment only when underdelivery is allowed on the line. In NetSuite, a transfer order is marked received by entering an item receipt against the open fulfillment. Each rule protects stock accuracy, and each leaves a person to explain the cases the rule did not catch.

## Worked example: one carton that never left

Illustrative only. A 410-person outdoor apparel retailer runs a distribution center and 38 stores. A transfer order sends 48 pairs of one boot style, packed as four cartons of 12, to a store ahead of a cold snap.

1. **Dispatch.** The picker scans three cartons, 36 units. The fourth carton is staged on the wrong dock door.
2. **Posting.** The shift lead posts the shipment for the full 48 so the truck can leave. The transfer now reads as complete at the shipping site.
3. **Receipt.** The store scans 36 units at the register. The receipt is short by 12.
4. **Investigation.** The inventory control analyst opens a case, compares the 36 dispatch scans with the 48 posted, and asks the distribution center for a spot count of the dock. The carton is found.
5. **Authorized action.** The inventory manager approves an adjustment returning 12 units to distribution center stock, reason code "posted not shipped", and a new 12-unit transfer.
6. **Checked result.** The store receives 12 units three days later. The transfer variance report for that store shows zero for the week.

What makes this valuable is the reasoning in step 4. Without the case note, a later reader sees a 12-unit adjustment and a second transfer, and cannot tell whether the carton was found, written off as shrink, or charged to a carrier. With it, the company can explain exactly how it handled a counting error that its systems did not catch. Recorded exception handling like this, with problem, decision and outcome attached, is the kind of operational history SourceX reviews when a company considers licensing its records for AI training and evaluation.

## Which record answers which question?

Map dispatch scans, store receipts and inventory adjustments to the questions a reviewer would ask about the case.

| Question about the case | Record that answers it | Usually held in |
|---|---|---|
| What was supposed to move? | Transfer order with lines and quantities | ERP or merchandising system |
| What physically left? | Dispatch scans by carton or unit | Warehouse system or handheld scanner log |
| What did the system say left? | Shipment posting with user and time | ERP transfer order history |
| What arrived? | Store receipt by line | Store POS or receiving app |
| Who looked into the gap? | Variance case, ticket or email thread | Ticket system, shared mailbox or spreadsheet |
| What was decided, and by whom? | Inventory adjustment with reason code and approver | ERP inventory journal |
| Did the fix hold? | Follow-up transfer receipt and weekly variance report | POS and ERP reports |

The middle rows are where histories often break. Scanner logs may be purged on a short cycle, and case notes often live in a mailbox rather than the ERP. Those gaps are worth knowing about before any introduction, because a history without the investigation shows a correction but not a judgment.

## Questions for the inventory operations head

Keep discovery at metadata level: what exists, how much, how long, which system and who owns it.

- How many transfers a year, and roughly what share end with a variance?
- Are dispatch scans kept at carton or unit level, and for how many years?
- Do variance cases have their own record, or are they handled in email?
- Do adjustments carry reason codes and an approver name?
- Which systems hold transfer history from before the current ERP?
- Who could authorize a discussion about licensing these records?

The [retail chain data guide](/guides/how-to-assess-business-data-opportunities-in-a-retail-chain) covers the wider set of retail record types, and the [logistics exceptions guide](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions) applies the same problem, action and result test to shipments.

## Does the company qualify, and what stays unknown?

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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.

Unknown until SourceX reviews it with the company: current buyer interest in this record type, the rights review result for employee and customer data, which records would be selected, and any offer. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. The [retail operations overview](/industries/retail-operations), the [inventory and fulfillment data type](/data-types/inventory-and-fulfillment) and the wider [industries hub](/industries) show related record types; [why data rights matter](/proof/why-data-rights-matter) explains the review.

## Go deeper on store transfer discrepancies

- [Store transfer discrepancy records across systems](/guides/store-transfer-discrepancies-records-across-systems): a join map from warehouse scans to POS receipts and ERP adjustments.
- [Who can license store transfer discrepancy records](/questions/who-can-license-store-transfer-discrepancies-records): a short answer on which executive to introduce.
- [Preserving store transfer history before consolidation](/guides/preserve-store-transfer-discrepancies-records): an inventory checklist for closing stores.
- [Store transfer discrepancy referral brief template](/resources/store-transfer-discrepancies-referral-brief-template): a fill-in template for the introduction.

## 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 a retailer can trace its short transfers from dispatch scan to closed variance, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the inventory operations head.

## 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