Online and off-site sales are promising the same stock
Pick a cutoff and reconcile every channel against one physical pool: confirmed online orders, pending online holds, off-site invoices or held stock, event reservations, manual adjustments, receipts, returns, damage, and loss. Shopify product records distinguish quantities such as available and committed, and inventory adjustment history can show time, attribution, reason, and quantity changes, but those records still need the merchant’s real channel exports and physical count to settle allocation. Do not assume each channel owns separate stock or that a sync feed guarantees no overselling. Before accepting another commitment, mark each unit as allocated, available, incoming only, damaged or unavailable, or unresolved, and give conflicts to the authorized inventory owner.
For: Authorized staff at a research-only merchant who sell the same physical stock through an online store and an off-site or in-person channel and suspect the same units are being promised twice.
Choose a reconciliation time and write it down before comparing systems. A website order export at noon, an event sheet at close, and a warehouse count at night cannot be treated as one picture without bridging movements between them. Record time zone, location, product identifiers, variations, and unit of measure for every record used.
State the allocation rule the business is actually using: first confirmed payment wins, first approved reservation wins, channel quotas, event stock set aside, or manual owner approval. If no written rule exists, say so and have the authorized owner choose one before staff improvise at the counter or in the online queue.
Do not infer physical separation from channel labels. Two sales surfaces can point to one shelf, and one surface can draw from several locations. The reconciliation begins with where saleable units physically are and which commitments already reduce them.
Read Shopify quantities as fields, not as a promise
Where Shopify is the online system, product and variant records can distinguish available, committed, incoming, and other inventory quantities, and Shopify recommends unique SKUs for tracking. Use the exact product and variant identifiers so an online line, an event line, and a warehouse bin describe the same item. A shared title or reused barcode is not enough for historical identity.
Available is a field state, not a guarantee that off-site staff did not already promise the same units. Committed quantities need to be traced to actual orders or reservations; incoming stock must not be counted as saleable unless it has actually been received into the pool under the merchant’s rule.
If a product was archived or hidden, treat that as a visibility change, not evidence about prior commitments or physical units. Keep historical orders, adjustments, and off-site records linked to the same identifier even when the public product is no longer actively sold.
Use adjustment history to explain movements, not to decorate them
Shopify’s inventory adjustment history can record time, activity, staff/app/channel attribution, quantity changes, and reasons such as counts, corrections, receipts, returns, damage, loss, and donations. Read it to reconstruct why the pool changed between the cutoff and now. Attribute each movement to a real person, app, channel, count, or document; where attribution is absent, record that gap.
Separate automatic decrements from confirmed online sales from manual corrections made after an event. A correction entered the next morning may describe an off-site sale, a counting error, damage, or an attempt to force the website back into line. The reason code and source document decide; the sign of the number alone does not.
Inventory movement is not equivalent to customer demand. Do not convert a negative adjustment into a verified off-site buyer, a return into sellable stock, or an incoming receipt into available units without the receiving record. Unknown causes remain unknown until the named owner supplies the source record.
Allocate commitments and stop new promises while conflicts are open
Build the allocation table at the cutoff: physical saleable pool; confirmed online commitments; online pending or held commitments under the store’s rules; off-site confirmed sales; off-site holds; damaged, lost, expired, quarantined, or otherwise unavailable units; and incoming stock excluded until received. Compare total commitments against saleable pool by product, variant, and location.
When commitments exceed saleable stock, identify the earliest unsupported promise and the records that created it. Pause new commitments for the affected identifier where the merchant’s authority allows, rather than selling through the conflict and hoping a sync corrects it. The inventory owner decides whether to fulfill, partially fulfill, substitute only if authorized, cancel, or reserve incoming stock, and support communicates only approved outcomes.
Assign durable fixes after the immediate allocation: identifier cleanup, channel reservation procedure, event stock control, adjustment reason discipline, or a scoped review of how orders and inventory connect. A Prism checkout-review inquiry can describe the observed channel conflict and records gap; confirm scope, responsibilities, fees, and terms before work. Technical sync capability, provider eligibility, and legal product questions remain separate.
Shared-stock allocation reconciliation
Use one cutoff for one product or variant and one location pool. Enter quantities only from records you can name, and mark unresolved causes instead of balancing by force. Keep customer lists, payment data, event contracts, and credentials outside this sheet.
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.
Shared-stock allocation reconciliation. The last column is for temporary notes.
Record or check
Decision it supports
Your finding and internal reference
Cutoff definition: date, time, time zone, product/variant identifier, location pool, and unit of measure.
Decision it supportsMakes online, off-site, and warehouse records comparable for the same units.
Physical saleable pool at cutoff: count source, count date, excluded damaged/lost/quarantined units, and receiving records since count.
Decision it supportsEstablishes the maximum units that can be promised before channel commitments.
Online commitments: confirmed orders, pending or held orders under the store’s rules, cancellations, and partial fulfillments.
Decision it supportsShows how much of the pool the online channel has already consumed or reserved.
Decision it supportsReveals promises made outside the online queue that must share the same pool.
Shopify quantity fields where applicable: available, committed, incoming, and identifier match for the product/variant.
Decision it supportsSeparates field states from physical proof and prevents incoming stock from being sold as on-hand.
Adjustment history: time, activity, staff/app/channel attribution, reason, and quantity change for each movement.
Decision it supportsExplains differences between systems without inventing demand or causes.
Allocation result: allocated, available, incoming-only, unavailable, and unresolved quantities at cutoff.
Decision it supportsIdentifies oversell risk and the earliest unsupported commitment before another sale is accepted.
Conflict decision and prevention owner: inventory owner, channel lead, fulfillment, support remedy, and procedure or review follow-up.
Decision it supportsAssigns who resolves affected buyers and who changes the reservation process.
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.
Limits
Shopify fields and adjustment history apply to Shopify records; a point-of-sale, marketplace, spreadsheet, or separate inventory tool needs its own current documentation.
Inventory movement is not proof of demand, receipt quality, product suitability, legal saleability, or fulfillment timing.
No synchronization tool is promised to prevent overselling, and this guide does not select or configure one.
Keep customer records, payment details, identity documents, private links, and credentials out of worksheets and public inquiries.
Shopify: Product details page — checked 2026-10-01. Shopify recommends unique SKUs for inventory tracking and product details distinguish available, committed, incoming, and other inventory quantities; archiving changes active sale visibility, not historical identity.
Shopify: Viewing inventory adjustment history — checked 2026-10-01. History can record time, activity, staff/app/channel attribution, quantity changes, and reasons such as counts, corrections, receipts, returns, damage, loss, and donations.
Prism solutions — checked 2026-09-21. Consultation scope, responsibilities, fees, and terms are agreed before work; no inventory-management capability or provider eligibility is implied.
Get help with store operations
Need help with the order, email or fulfillment step itself?