Shopify purchase order / PO receiving stuck or inventory not updating — Plus purchasing, suppliers, receiving.

Several products can look like “stock never arrived.” They do not share a settings panel. This page is only when a Shopify Plus purchase order / PO will not receive — or Receive runs but Available inventory at the receiving location does not increase. Moving stock between your own warehouses / stores is transfer order not receiving. Ongoing POS vs online drift without a PO document is POS inventory not syncing. Customer-facing draft order payment email silence is draft order invoice not sending. Logged-in company buyers seeing wrong catalog prices is B2B catalog prices wrong. This page is only: Shopify purchase order / PO receiving stuck or inventory not updating (Plus purchasing, suppliers, receiving).

Six ordinary reasons Receive fails while the rest of the store looks fine: the PO is still Draft / never marked Ordered; Receive is missing because staff lack purchasing permissions; supplier SKU is not mapped to the Shopify variant; receiving location is wrong; Incoming shows the qty but Available never rose (or you received zero / overrode to zero); or you are debugging a transfer between owned locations / POS sync / draft invoice / B2B catalog instead of the purchase-order timeline. Walk them in that order. You already pay for Shopify Plus purchasing. You do not need another “procurement SaaS” to finish Receive on the PO you already created.

Open Products → Purchase orders (Shopify Plus purchasing) and open the stuck PO. Screenshot: supplier, expected arrival, receiving location, line quantities / costs, and status (Draft, Ordered, Partially received, Received, Canceled). Confirm the PO was marked Ordered / sent to the supplier — Draft POs often cannot fully receive into Available.

Use Receive / Add to inventory on the PO. Enter the quantities that actually arrived (partial receive OK). Confirm the receiving location matches where warehouse staff counted the boxes. If Receive is missing, check staff permissions for purchasing / inventory at that location and that the shop is on Plus with purchasing enabled. Honest fork: if the document is an inventory transfer between your own locations (not a supplier PO), leave this page and use transfer order not receiving. If a customer draft invoice email never sent, that is draft order invoice not sending.

After a successful receive, open the variant → Inventory and confirm Available at the receiving location increased by the received qty. Incoming / on-order / committed / unavailable buckets can hide “why the floor still shows zero” even when the PO shows Received. Re-check the supplier item ↔ variant mapping if a line received against the wrong SKU.

Staff: Settings → Users and permissions — purchasing create / receive often needs inventory manage rights at the receiving location. Apps / 3PLs that auto-create POs can leave documents Draft until a webhook succeeds — check the app’s purchasing queue before editing stock by hand. If company buyers see wrong prices after stock arrives, that is catalog pricing, not PO receive — B2B catalog prices wrong.

Checklist: (1) screenshot PO status + supplier + receiving location, (2) confirm Ordered (not stuck Draft), (3) Receive with real arrival quantities (partial OK), (4) verify variant inventory Available at that location, (5) confirm supplier SKU mapped to the correct variant, (6) if an app owns the PO, check its logs before manual adjust.

Prove it: same SKU, receiving-location Available up by received qty, PO status Received or Partially received matching the lines. If stock only moved between your own locations and there is no supplier PO, switch to transfer order not receiving. If POS still disagrees after Available rose, open POS inventory not syncing.

Inventory transfer between owned locations is transfer order not receiving. POS / online drift without a stuck PO is POS inventory not syncing. Customer draft order invoice email silence is draft order invoice not sending. Wrong company catalog prices are B2B catalog prices wrong. None of those finish Receive on a Plus purchase order that is still Draft / Ordered without a successful receive.

Finish PO status → Ordered → receive → receiving-location Available proof first. Only then open the related playbook that matches the remaining symptom.

Stay DIY if you can spend one afternoon on the list above: prove PO status, finish receive, clear supplier mapping + location ledger confusion, and stop treating transfer orders / POS sync / draft invoices / B2B catalogs as the same bug. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: transfer order, POS inventory sync, draft invoice, B2B catalog prices.

Pay for help when the work is not the Purchase orders screen — it is connecting the stack you already have so lead capture is not dying in DMs, PO / receive exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a purchasing-app retainer, not a conversion guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or inventory-uptime claim.

What it does not buy: more orders, automatic supplier EDI, a purchasing app license, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.