Ship From Store and Endless Aisle: Selling the Stock You Already Own
Most Australian retailers hold more stock in their shops than in their warehouse, and almost none of it is visible to the website. Ship from store makes each shop a fulfilment point. Endless aisle lets a customer buy an item the shop in front of them does not have. Both are routing problems before they are software problems.
The technology is the easy half. The hard half is deciding which store should get each order, what happens when that store cannot fulfil it, how much picking a shop can absorb on a Saturday, and how you stop a bad count in one store turning into a cancelled order and a refund. This page covers all of it.
Realistic ROI
Four Decisions That Decide Whether Store Fulfilment Works
Retailers who abandon ship from store almost never do so because the integration failed. They abandon it because one of these four was never settled.
What the routing rule is actually optimising for
Nearest store, cheapest freight, oldest stock, slowest selling location, highest stock cover, or the store that will still hit its own sales budget. These pull in different directions and the business has to choose, in order, with weightings. A routing engine with no agreed objective just distributes work unpredictably and every store manager believes they are getting more than their share.
How long a store gets to accept before it moves on
A store cannot watch a screen all day. Orders need an acceptance window, an escalation when it expires, and an automatic re-route to the next best location rather than silence. Without a timer, orders sit in a shop that is short staffed on a Tuesday and the customer finds out three days later that nothing has happened.
Whether the store is paid for the work
If a shop picks, packs and loses the stock from its own floor but the sale is credited to the online channel, staff will find quiet ways to reject orders. Sales attribution, commission treatment and stock transfer accounting are not finance details to be sorted later. They determine whether the operational design survives contact with the roster.
How accurate the store count really is
Ship from store converts every counting error into a customer facing failure. Before routing a single order, you need a view of shrinkage, negative on hand records, unreceipted transfers and layby or held stock that the system still counts as sellable. Buffers and exclusions come from that picture, not from a guess.
What the Integration Has to Do
Six moving parts sit between an order arriving and a parcel leaving a shop. Each one has a failure mode worth designing for.
Store level availability
The website has to see stock by location, not one blended number. That means location aware feeds from the point of sale or ERP, per location buffers, exclusion of display units, layby, held and damaged stock, and a rule for what happens when a location goes offline. A single national quantity is why most retailers think they cannot do this.
Routing and scoring
Each order line is scored against candidate locations using distance to the customer, stock cover at that store, the store’s open pick queue, freight cost to the destination, and whether the item is selling well there. The output is a ranked list, not a single answer, so a rejection has somewhere to go immediately.
Acceptance and rejection
Staff get a short, unambiguous task on a device they already carry: what to pick, from where, by when. Rejections require a reason code, because reasons are data. A store that rejects for not found repeatedly has a stock accuracy problem worth fixing, and a store that rejects for too busy needs its capacity limit adjusted rather than a talking to.
Capacity and cut offs
A shop can absorb a set number of parcels a day, and fewer on a trading Saturday. Capacity caps, courier cut off times per location and public holiday calendars per state all belong in the routing logic. Without them, the network sends the busiest store the most work because it also holds the most stock.
Carrier handover from the shop
Labels have to print in store from the same carrier account as the warehouse, with the store as the sender address and the correct return address. Consignments need to be manifested before pickup, and someone has to know what happens when the driver does not arrive. Getting this wrong turns a fulfilment win into a shop full of unscanned parcels.
Endless aisle ordering
A customer in a shop, or on the site, buys an item held at another location or on order from a supplier. The commitment made at that moment is a delivery promise, so the integration has to expose a realistic date from incoming purchase orders and transfer lead times, not an optimistic default. Honest dates are also an Australian Consumer Law issue, not just a service one.
Common Scenarios and How They Should Behave
| Task | Traditional | Integrated Properly | Notes |
|---|---|---|---|
| Online order, item only in shops | Cancelled or backordered | Routed to the best store | The single largest source of recovered revenue in most networks, and the reason the project usually pays for itself. |
| Store cannot find the item | Order sits, customer chases | Rejected with a reason, re-routed in minutes | The reason code feeds a stock accuracy report per store, which is how the rejection rate comes down over time. |
| Order split across two locations | Manual decision by a person | Split only when the value justifies it | Splitting doubles freight. Set a threshold so low value orders wait or route whole rather than split by default. |
| Customer in a shop wants a size held interstate | Take a name and call around | Sold on the spot with a real date | Attribution matters here. The selling store should keep the sale or the behaviour stops within a fortnight. |
| Item on order from the supplier | Not offered at all | Sold against a confirmed inbound date | Only expose incoming stock where supplier dates are reliable, and state the date plainly at checkout. |
| Saturday trade in a busy centre | Store swamped with picks | Capacity cap diverts to quieter stores | Spreads the labour to locations with time, which is usually also where the slow moving stock sits. |
| Last unit in the store | Sold twice, once online once at the till | Buffered or held on allocation | Per location buffers on final units are cheap protection against the worst customer experience in retail. |
| Regional delivery from a metro store | Freight cost discovered later | Freight cost included in the routing score | Remote area surcharges and cubic weight can make the nearest store the wrong answer. Score on landed cost. |
Where Store Fulfilment Programmes Come Unstuck
Routing before the counts are trustworthy
If store counts are wrong, ship from store publishes that fact to customers at scale. Start with a small group of stores that have had a recent stocktake, hold back final units with a per location buffer, and expand only as measured rejection rates fall. Retailers who switch the whole network on at once almost always switch it back off.
The store carries the cost and the channel takes the credit
Decide in advance how the sale is attributed, whether the store is credited at retail or cost, and how the stock movement is recorded between locations or entities. In a franchise or multi entity group this is a real transfer with real GST consequences, not a reporting preference, and it needs the accountant in the room before the software is configured.
No capacity limits, so the network self destructs on peak days
Peak trading is exactly when stores have the least spare labour and the most orders. Set per store daily caps, tighten them on high traffic days, and let the routing degrade gracefully to the warehouse or a quieter store. A cap that stops a shop taking on work it cannot do is protecting the customer promise, not avoiding effort.
Delivery promises that the network cannot keep
Under the Australian Consumer Law, a delivery timeframe presented at checkout is a representation. A promise built on optimistic transfer times or unconfirmed supplier dates becomes a misleading representation the moment it slips. Publish the date the network can actually hit, including the store pick window and the carrier cut off, and update the customer when it changes.
Parcels shipped from a shop with no returns path
A customer who receives a parcel posted from a suburban store will often try to return it to their nearest store, which may be a different one. Decide where returns are received, how the stock is put back into the right location, and how the refund is processed against the original channel. Returns handling designed after launch is how stock ends up stranded in the wrong shop.
Nobody owns the exceptions
Rejected orders, expired acceptance windows, unmanifested consignments and stock adjustments all need a named owner and a daily queue. Store fulfilment generates exceptions in shops, where there is no operations team watching a screen. If head office is not looking at that queue every morning, the failures are found by customers instead.
How Yes AI Approaches Store Fulfilment
Stock accuracy assessment first
We measure what your locations actually hold against what the system says before proposing a routing design, including negative quantities, stale transfers and held stock. If the honest answer is that your network is not ready, we will say so and scope the counting work instead of selling you a routing engine.
Routing rules written in business language
The scoring weights, capacity caps, cut offs and fallbacks are documented so a retail operations manager can read and change them, not buried in code. You approve the rules before anything routes, and you can adjust them by season without a development request.
Built on a managed cloud automation layer
The connections between your point of sale, ERP, online store and carriers run on infrastructure we operate and monitor, with record level logging of every routing decision. When a store asks why it received an order, there is an answer with the score behind it.
Rejection and capacity reporting from day one
Rejection rate by store and reason, average pick time, capacity utilisation and re-route counts are reported weekly. This is how a programme improves rather than quietly stalls, and it is usually the report that tells you which store needs a stocktake.
From Warehouse Only to a Fulfilment Network
Five steps. A pilot group of stores is typically live in six to eight weeks.
Measure the opportunity and the accuracy
How much stock sits in stores, how often the website turns away demand it could have filled, and how accurate each location’s counts are. That gives both the business case and the readiness picture in the same exercise.
Agree the routing objective
We work through the trade offs between speed, freight cost, stock cover and store workload, and turn the answers into a weighted scoring rule with capacity caps and cut offs per location.
Wire location level availability
Stock by location flows from the point of sale or ERP to the online store with buffers and exclusions applied, so the site sells what is genuinely sellable at each shop rather than a national total.
Pilot with a handful of stores
A small group of accurate, willing stores runs live orders with acceptance windows, rejection reasons, in store labelling and carrier handover. We tune the rules against real behaviour before widening.
Extend, then add endless aisle
Roll out to the network with measured rejection rates, then open up selling stock held elsewhere or inbound from suppliers once the delivery dates behind those promises can be trusted.
Related Reading
SaaS Integration Explained
The patterns behind any system to system connection.
Click and Collect Integration
When the customer comes to the stock instead.
Multichannel Inventory Sync
One stock pool across web, shops and marketplaces.
Freight and Carrier Integration
Rates, labels and manifests, including from stores.
Preorder and Backorder Management
Selling stock that has not arrived yet, honestly.
Peak Season Readiness
Getting the network through November and December.
FAQ
Put the Stock in Your Shops to Work
Book a call. We will measure how much sellable stock is invisible to your website, assess whether your counts are ready, and give you a routing design and a priced plan. The assessment is yours either way.
All discussions held in confidence. Australian-based consultants.