A Reorder Suggestion Needs an Incoming-Stock Line Before It Becomes a Purchase Order

A low stock number can look urgent while a supplier shipment is already on its way. A simple incoming-stock check gives merchants a visible way to challenge a reorder suggestion before it creates excess inventory.

A Reorder Suggestion Needs an Incoming-Stock Line Before It Becomes a Purchase Order

A reorder recommendation can be mathematically tidy and commercially wrong. The usual reason is simple: the stock view sees what is on the shelf, while the supplier commitment lives somewhere else.

A Shopify community request makes the gap concrete. The merchant wanted a Sidekick-generated custom app to use sales velocity, stock levels, and lead times for reorder suggestions. The app could not access purchase orders, so it could miss products already ordered and in transit. The stated risk was an unnecessary second purchase and potential overstock. A response suggested a practical workaround: total the quantities on open purchase orders and write that value to a product field that the app can read. The discussion is one merchant's account, rather than evidence that every store has the same limitation. It identifies a real decision problem.

Stock on hand answers one question: what can be sold or counted at this location? A reorder decision asks a different one: what supply will be available before the next period of demand is over? A purchase order or transfer can be part of that answer, provided its expected arrival is credible.

The useful small-business opportunity is an incoming-stock reorder check. It is a bounded review of one location, a selected SKU sample, and the path from supplier commitment to a forecast input. The goal is an explainable buying decision. It does not replace a merchant's purchasing judgment, supplier relationship, or inventory platform.

A low shelf count and a low supply position are different facts

Shopify defines Incoming inventory as units on their way from transfers, purchase orders, or apps. Those units are not available for sale until received at the location, at which point they become Available. Its documentation also explains that a purchase order can link to an inventory transfer for tracking a supplier shipment. Shopify's inventory-state guide and purchase-order guide describe those states and links.

That distinction matters in a plain example. A retailer has 12 units of a fast-selling water bottle available. Its buying rule targets 40 units to cover the next demand window. A screen that sees only available stock suggests 28 more units. A supplier has already confirmed 24 units that should arrive before the window ends. The relevant gap is four units, subject to demand, timing, and the reliability of that arrival date.

The calculation is intentionally modest:

reviewed purchase quantity = target coverage − available units − eligible incoming units

Eligible incoming units means units tied to a live purchase order or transfer whose expected arrival falls inside the decision horizon and whose quantity has not already been received or rejected. If the result is below zero, the proposed purchase quantity is zero for this review. The calculation does not predict demand. It exposes a missing supply input before a person approves a new commitment.

The time limit matters. A shipment expected after the business needs stock for a promotion, season, or normal replenishment cycle cannot solve the near-term gap. An arrival date supplied by a vendor can also be wrong. The ledger should make that uncertainty visible instead of treating every outstanding quantity as guaranteed stock.

The check has four records, each with a different job

The service can use existing Shopify views, a simple controlled spreadsheet, or a custom field that an approved app reads. The format is less important than the relationship between four records.

1. The purchase commitment. Capture the SKU, ordered quantity, supplier or transfer reference, purchase-order state, and expected arrival. This record establishes that the business has promised to buy units. It does not establish that they have reached the shelf.

2. The inventory state. Capture available, committed, unavailable, and incoming quantities for the relevant location. A multi-location business should avoid combining numbers from another warehouse unless that stock can actually be transferred in time. A quantity without a location can make a forecast look safer than the fulfilment operation feels.

3. The forecast input. Record which incoming quantity the recommendation can read and when it was refreshed. The community workaround describes flattening the total of open purchase orders into a custom variant field. That can be useful as an input, yet it needs a stated rule: which purchase-order statuses count, whether partial receipts reduce the value, and how an arrival date affects eligibility.

4. The reviewed recommendation. Record the target coverage, available units, eligible incoming units, proposed quantity, reviewer, and decision. This is the layer that lets a buyer explain why a purchase was deferred, reduced, or approved despite incoming stock.

The four records turn a vague instruction to “include incoming stock” into a traceable decision. A mismatch can be diagnosed. Perhaps a purchase order was cancelled, a transfer is late, an expected date is blank, a partial receipt was never recorded, or the custom field is stale. Each explanation points to a different next action.

Sidekick makes the boundary visible

Shopify describes Sidekick as an assistant that can help merchants manage a store and generate custom apps. Its documentation gives reorder recommendations based on sales velocity as an example of what a generated app may do. The same documentation lists the Admin API elements available to such apps: orders, products, customers, discounts, content, and analytics. Purchase orders do not appear in that listed set. Shopify's Sidekick app-generation documentation supports the boundary described in the community request.

This does not make the tool unreliable in every context. A store with simple replenishment, no open supplier orders, or a separate manual buying routine may find the existing recommendation adequate. It does mean the owner should ask what information reaches the recommendation before treating it as a purchase instruction.

That question applies beyond one assistant. Many reports and dashboards simplify inventory to a single available number. A useful review identifies the source, refresh timing, location, and state of every quantity used to recommend a buy. The more automatic the recommendation appears, the more valuable that short audit trail becomes.

Where the platform earns money, and where a reviewer fits

Shopify operates a broad commerce platform. Its 2025 Form 10-K reports US$378.4 billion in gross merchandise volume for 2025. That is commerce flowing through merchants on the platform, rather than Shopify's own product revenue. The filing explains that Shopify earns subscription solutions revenue and merchant solutions revenue, including payments and other services. Shopify's 2025 Form 10-K gives the company-wide figures and model.

A freelancer should not present a four-column stock check as an alternative to that platform. Shopify supplies the commerce infrastructure, integrations, inventory records, and account controls. A mature retailer may also use an ERP, warehouse system, or specialist planning tool with capabilities outside this narrow review.

The accessible layer is preparation. An inventory-aware operator can sell a fixed input review for a small retailer that already uses Shopify and keeps seeing uncertain reorder suggestions. The client pays for a scoped map of a selected SKU sample, a clear incoming-quantity rule, a reviewed calculation, and a test record. The client approves every eventual purchase and keeps control of its vendor data, account access, and operational decisions.

The best fit is a store with recurring supplier orders, several active SKUs, and a person who feels the cost of ordering twice. It is a poor fit for a new store with no purchase history, a catalogue whose goods are made only after customer payment, or an operator who cannot maintain even approximate expected-arrival information. The starting point is an existing decision problem, rather than a general invitation to automate inventory.

Test four SKUs before changing a live reorder rule

Use fictional products in a test store or a local working sheet. Avoid copying customer data, supplier prices, or production credentials into a sales demonstration. Make four SKU cases with a stated target coverage and decision horizon.

No incoming quantity. Give the first SKU low available stock and no open commitment. The adjusted calculation should match the basic shortage. This is a control that confirms the check does not invent supply.

Arrival inside the horizon. Give the second SKU low available stock and an open incoming quantity expected before the target coverage window ends. The eligible incoming quantity should reduce the proposed purchase amount. Record the reference and expected arrival behind the number.

Arrival outside the horizon. Give the third SKU an incoming order that arrives after the planned demand window. Keep it visible, yet exclude it from eligible incoming quantity for the immediate decision. The buyer may still decide to order less for another reason; the record should say why.

Partial receipt. Give the fourth SKU an original commitment of 30 units, with 10 received and 20 still expected. The ledger must reduce the remaining incoming quantity to 20. This case catches a common double count: treating the original order and the received stock as separate supply.

For each case, compare a recommendation based only on available units with the reviewed result. Write down the target, available quantity, eligible incoming amount, date rule, result, and reviewer decision. The point is not to prove a particular forecast is correct. It is to prove that a person can see which commitments affected the decision.

The test gives a useful stop rule. End the review if Shopify's existing view already delivers the needed information in a way the buyer can apply, or if expected arrival dates are too unreliable for incoming units to be used as a planning input. In the latter case, the next task may be supplier-date discipline, rather than a custom field or app.

Avoid three shortcuts that turn supply data into fiction

Avoid counting every open purchase order as usable supply. Cancelled lines, partial receipts, rejected goods, uncertain deliveries, and stock intended for a different location can make the total misleading. The check needs a stated inclusion rule.

Avoid overwriting the source record with a number nobody can trace. A convenient product field should link back to the purchase order or transfer references that produced it. A stale field can be more dangerous than a missing field because it looks authoritative.

Avoid letting a forecast place an irreversible supplier order without a human review. The calculation can challenge a recommendation. It cannot know a supplier's true reliability, a product's substitute demand, warehouse capacity, cash constraints, or an upcoming promotion unless those facts have entered the decision deliberately.

The purchase decision needs a visible arrival assumption

The complaint about purchase-order access reveals an ordinary inventory problem, not merely an AI feature request. Available stock and ordered stock tell different parts of the supply story. A useful reorder recommendation needs both, with the date and location assumptions exposed.

For a small service provider, the honest offer is a bounded incoming-stock check. Build the four records, decide which incoming quantities qualify, test four fictional SKUs, and let the inventory owner approve every purchase. If the merchant already has a clear and reliable view, the right conclusion is to preserve it. If the test reveals a blind spot, the business can improve its buying decision before turning a low shelf count into an unnecessary supplier commitment.

Sources