A return was added to inventory by two different systems

Start from the physical receipt, not the stock totals

Open the receiving record for the return first: the parcel reference, the date it was logged, the items and the counted quantity. That record is the anchor for everything else. A return can legitimately produce a restock entry in the returns portal and a receipt entry in the warehouse system, and both can point at the same physical goods.

Before any arithmetic, establish which system holds the authoritative stock balance for that item and location, and how the two systems relate. In some setups one system mirrors the other's entries, so the same addition visible in both places changed the balance once, not twice. In others each system keeps its own book for its own purpose, and only one of them feeds the storefront. Two visible increases are a reason to investigate, not proof that physical stock was added twice.

Do not start by comparing the two systems' totals against each other. A doubled increase tells you something is wrong; it does not tell you which entry is wrong, or whether either entry is wrong in isolation. Write down how many units the parcel contained and which order or return they belong to, and treat that as the quantity the authoritative balance should reflect.

If no receiving record exists, the investigation changes: you are no longer reconciling two additions against one receipt, you are missing the receipt itself. Record that gap and follow the merchant's returns-receiving process rather than treating either software entry as proof that goods arrived.

Read each restock event in its own system's records

For a Shopify store, the inventory adjustment history records the time of each change, the activity, the staff member, app or channel attributed to it, and the quantity change. Its documented reasons include counts, corrections, receipts, returns, damage, loss and donations, and the history can contain both automatic and manual changes. That attribution is the first clue: an entry created by a returns app and an entry created by a warehouse integration are two records of activity, not necessarily two physical events.

Read the equivalent record in the warehouse or fulfillment system on its own terms: the receiving or adjustment entry, its reference, the quantity accepted and the final quantity it produced. Do not assume the two systems use the same vocabulary. One system's return and the other system's receipt may be the same event described twice, and one system's correction may be a deliberate fix for an earlier error rather than a second arrival.

Note how each entry was triggered where the record shows it. An automatic entry created when a return was marked received in the portal, and a second automatic entry created when the warehouse scanned the same parcel, is a recognizable duplicate pattern. A manual entry created by a staff member needs a different question: what instruction was that person following?

Link both events to the same goods before calling them duplicates

Two similar adjustments do not prove two physical items arrived, and they also do not prove a duplicate. Establish the link from each side: the order or return reference on the portal event, the parcel or return reference on the warehouse event, and the item and quantity on each. If both events identify the same return and the same units as the single receiving record, they represent one receipt recorded twice.

Check the timing and sequence. A portal entry that preceded the parcel's arrival, followed by a warehouse entry at receipt, suggests the portal recorded an expectation rather than a count. A manual correction entered days later may have been someone's attempt to fix the doubling, which means the current total might already be right even though the history looks alarming.

Where the events identify different returns, different items or different quantities, stop treating them as duplicates. Two genuine returns of the same product on the same day is a real possibility. The conclusion must be drawn from the references on the actual records, not from the coincidence of matching quantities.

Choose the correction and its owner separately from the audit trail

Once the match is established, isolate what the two linked return events did to the confirmed authoritative balance. Add the quantities of the two linked writes that actually posted to that balance, subtract any earlier correction already entered against this same excess, and compare the remainder with the counted quantity from the receiving record: the excess over the count is the correction the authorized inventory owner needs to approve. Do not take the raw difference between the balance before the return and its current value, because unrelated receipts, shipments, transfers and other movements in between would be swept into that difference; if you work from balance totals instead of the two entries, reconcile every intervening movement first and remove those unrelated effects before comparing with the physical count. If one entry merely replicated the other, or each system keeps a separate book, there is no doubling to subtract and the investigation turns to why the records looked duplicated. State any correction as a specific item, quantity and location, and identify which system's figure should be regarded as the accurate one going forward.

The correcting entry is a new, recorded adjustment with its own reason, attributed to the person making it. Do not delete or overwrite either original event. The history is what allows the next person to understand why the total changed, and Shopify's adjustment history exists precisely so that counts, corrections and receipts remain distinguishable. A clean-looking total with a destroyed trail is worse than a corrected total with an honest one.

Keep this inventory decision separate from any question about whether the returned units may be resold. This reconciliation decides how many units the records should show; the disposition of the goods is the responsible owner's separate decision under the merchant's applicable procedures.

Record the conclusion so the next reconciliation starts from facts

The closed record should let another authorized staff member answer: which return and parcel were involved, what each system added, which balance each write actually changed, which movement was accepted as the receipt, what correction was authorized and by whom, and what was done about the process that allowed the double entry. If the same returns app and warehouse integration repeatedly both add stock, that recurrence is an integration configuration question for whoever maintains those systems.

If the recurring double-restock touches the storefront's available-to-purchase quantities and you want help scoping that website-side question, a Prism consultation can start from a description of the platforms, the two event types and the mismatch, without order exports or customer records. Scope, responsibilities, fees and terms are confirmed before any work; the inventory correction itself remains with your authorized staff.

Duplicate-restock match sheet

Use one copy per physical return. Enter actual references and findings in the final column. The sheet decides which recorded movements represent one receipt and confirms which balance those movements actually changed before any subtraction is proposed; it does not decide whether the goods may be resold, and it never deletes an audit entry.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.