For retailers, brands and wholesalers who have never had to pull a product and want to be ready

Product Recall and Stop Sale: Pulling a Product From Every Channel in Minutes, Not Days

The first hour of a product recall is not about press releases. It is about making sure nobody sells another unit. In a business with four stores, a Shopify site, a marketplace listing and a wholesale portal, that means five or six separate systems, each with its own way of taking a product off sale, and usually one person who knows how to do it in each.

Then come the harder questions. Who bought it? Which batch? Which retailers did we wholesale it to? Where is the remaining stock physically sitting? How do we contact customers who checked out as guests, and what do we say? This page covers how to wire your systems so a recall becomes a controlled procedure instead of a scramble, what the Australian Consumer Law expects at a general level, and why for many smaller retailers a well written manual runbook is the right first step.

Book a Recall Readiness Call (03) 9003 0111

Recall Readiness in Numbers

1 action

Should stop sale everywhere

One flag in the system of record that every channel obeys, rather than five logins and a checklist

2 days

Mandatory report window

Under the ACL, suppliers must notify the ACCC within two days of learning of a death, serious injury or illness associated with a consumer good. General information only

3 lists

Every recall needs

Customers who bought it, businesses you sold it to, and every location holding stock

0 guesses

On which batch was sold

Only possible when batch or serial data travels with the sale, not just the SKU

Why Recalls Expose Every Gap Between Your Systems

Day to day, small inconsistencies between POS, website and ERP are an annoyance. During a recall, every one of them becomes a unit that should not have been sold or a customer you cannot reach.

Every channel takes a product off sale differently

Your POS might need the item set to inactive or blocked at the register, your website needs the product unpublished or set to unavailable, your marketplace listing needs to be ended or set to zero, and your B2B portal needs the item hidden from trade customers. If your ecommerce platform simply sees zero stock it may show a sold out badge and keep the page live, which is not the same as withdrawing it. Each of these is a different action in a different system, often requiring a different person.

Finding buyers depends on data you may not have kept

Online orders carry a name, email and delivery address, so identifying online buyers is usually possible. In store sales are different. Unless the customer was attached to the sale through a loyalty account, a digital receipt or a trade account, the POS knows a unit was sold but not to whom. Recall planning starts by understanding which share of your sales you can actually trace to a person, and that answer shapes the public notice you will need.

Batch level recalls need batch level sales data

Many recalls cover a specific batch, lot, date range or serial number range rather than every unit of a product. If your systems record only the SKU on each sale, you cannot tell which customers received the affected batch, so you end up recalling everything and contacting everyone. Carrying batch or serial data from receipt through to the sale is the single biggest difference between a precise recall and a blanket one.

There are legal obligations and a clock

At a general level, the Australian Consumer Law requires suppliers to notify the responsible Commonwealth minister, through the ACCC, within two days of becoming aware that a consumer good they supplied has been associated with death, serious injury or serious illness. Voluntary recalls must also be notified to the ACCC within two days of taking the action. Food recalls are coordinated through Food Standards Australia New Zealand and state food authorities, and therapeutic goods through the TGA. Systems do not make those decisions, but they decide how fast you can act once a decision is made. This is general information, not legal advice.

The Six Parts of an Integrated Recall Workflow

Each part is useful on its own. Together they turn a recall from a week of spreadsheets into a procedure you can rehearse.

Off sale everywhere

One stop sale flag

A single recall or stop sale status is set in the system that owns the product record, usually the ERP or inventory system, at product level or for a specific batch or serial range. The integration layer then pushes the correct action to every channel: block at the register so a scan produces a warning instead of a sale, unpublish or hide on the website, end or zero the marketplace listing, hide from the trade portal and pause any advertising feed. Each channel confirms it has applied the block, and any channel that fails to confirm raises an alert within minutes rather than being discovered later.

Nothing ships

Open orders caught in flight

Orders already placed but not yet dispatched are the most commonly missed exposure. The workflow finds open web orders, click and collect orders awaiting pickup, preorders, backorders, subscription orders scheduled to renew and wholesale orders in the warehouse queue, places them on hold and routes them to customer service. Messages to the warehouse or third party logistics provider cancel or hold picks that have not left the building, and anything already handed to a carrier is listed for follow up.

Who to contact

Affected customer list

Order history from ecommerce, POS sales linked to a customer, loyalty purchases, marketplace orders and trade invoices are combined into one list for the affected product or batch and date range, with contact details, quantity, purchase channel and purchase date. Duplicates are merged where the same person bought through more than one channel. The list also reports how many units were sold anonymously, which tells you whether direct contact alone can reach most buyers or whether a public notice in store and online is essential.

Retailers you supplied

Downstream businesses

Wholesalers and brands have a second audience: the retailers, distributors and marketplace sellers they supplied. Invoices and dispatches for the affected product and batch identify each business, the quantity shipped and the date. Each receives a recall notice with instructions on removing stock from sale, quarantining it and returning or destroying it, and their acknowledgement is tracked so you know who has acted and who needs a phone call.

Consistent remedy

Notices, returns and refunds

Recall notices go to affected customers by email and SMS using the wording approved for the recall, with a clear description of the product, how to identify the affected batch, the risk, what to do and the remedy offered. Returns are logged against the recall reference in POS and ecommerce so refunds, repairs or replacements are recorded consistently, regardless of where the customer bought or returns the item, and the returned quantity is visible against the sold quantity.

Auditable record

Quarantine stock and evidence trail

All remaining stock is moved to a quarantine status or location in every store, warehouse and third party logistics site so it cannot be picked, transferred or counted as available. Returned units go to the same status. The workflow keeps a timestamped log of when the block was applied in each channel, which orders were held, which notices were sent and delivered, which retailers acknowledged and how many units were recovered. Regulators commonly ask about recall effectiveness, and this log is how you answer.

Recall Situations and How Integrated Systems Respond

Task	Traditional	With a Recall Workflow	Notes
Supplier advises of a faulty batch	Email forwarded around, products pulled store by store	Batch flagged once, blocked in every channel	The block should apply to the batch if your systems carry batch data, or to the whole product if they do not.
Recalled item scanned at a register	Sold, because nobody updated that store	Register warns and refuses the sale	Most POS systems can block or warn on an item. The integration makes sure every store receives the flag at the same moment.
Web orders placed before the recall	Shipped by the warehouse as normal	Held automatically and passed to service	Includes click and collect orders sitting on the pickup shelf, which are often forgotten.
Identifying in store buyers	Unknown, rely on a public notice	Loyalty and receipt linked sales listed	Anonymous cash and card sales remain untraceable. The list shows how many, so the public notice can be sized properly.
Wholesale customers who stocked it	Sales reps ring around from memory	Notice sent and acknowledgement tracked	Retailers who have not acknowledged after a set time are escalated to a person for a call.
Customer returns item to another store	Refund processed as an ordinary return	Return tagged to the recall reference	Tagging matters for recall effectiveness reporting and for any claim against the manufacturer or supplier.
Marketplace listing still live	Noticed days later by a customer	Listing ended with the other channels	Marketplaces may also run their own recall processes and expect sellers to act quickly.
Regulator asks how many units recovered	Spreadsheet rebuilt from several systems	Sold, returned and quarantined totals reported	A recall effectiveness figure is only credible if the sold quantity is credible, which depends on clean sales data.

Where Recall Workflows Fail

Zero stock is not the same as withdrawn

Setting inventory to zero is the fastest way to stop online sales, but it often leaves the product page live with a sold out badge, keeps any back in stock or preorder mechanism active, and can be overwritten by the next stock sync from the warehouse, which still shows units on hand. The stop sale flag must be a separate status that the stock sync respects, not a stock quantity that the next sync can restore.

The register is the last place to hear

Store POS systems often receive product updates on a schedule, sometimes overnight, and some registers keep working offline from a local cache. A recall flag applied in the morning may not reach a register until the next day. Find out how quickly your POS propagates an item block to every register, whether offline registers honour it, and pair the system block with a direct message to store managers in the first hour.

Batch data stops at the warehouse door

Many businesses track batches in the warehouse or ERP but sell by SKU, so the batch is lost at the point of sale or at the website order. If that is your situation, plan for product level recalls until batch data is carried further. Pretending you can do a batch level recall when the sales data does not support it leads to customers being missed, which is worse than contacting everyone.

Using customer data for a recall without thinking about privacy

Recall notices are generally a legitimate and expected use of customer contact details, and the Australian Privacy Principles allow use for a related secondary purpose the individual would reasonably expect, among other grounds. That does not make the recall list a marketing list. Send recall messages as recall messages, keep the list access controlled, do not add promotional content and do not use it later for campaigns. Get advice if you are unsure how APP 6 applies to your situation.

Automated messages before the wording is approved

The integration should be able to send notices to every affected customer within minutes, but only after the content has been approved by whoever owns the recall, often with input from the supplier, the manufacturer and sometimes the regulator. A message sent with the wrong batch numbers or the wrong remedy is difficult to correct. The send step should require explicit approval, while list building and stop sale run immediately.

No rehearsal until the real thing

Recall workflows that have never been exercised tend to fail on something mundane: an expired login, a channel nobody remembered, a store on an old POS version, a template with broken links. Run a mock recall on a harmless product once or twice a year, time each step, and fix what breaks. Many quality and food safety programs expect mock recalls anyway, and the systems part should be part of that exercise.

How Yes AI Approaches Recall Readiness

We start with a runbook, not a build

For a single store or a business with one website, a clear written procedure listing every system, who does what and in what order is often enough. We will write that first, test it with you, and only recommend automation where the runbook shows a step is slow, error prone or dependent on one person.

One flag, every channel

Where automation earns its place, we connect the stop sale flag in your system of record to each POS, ecommerce store, marketplace and trade portal through a managed cloud automation layer we operate, with confirmations from each channel and alerts when any of them fails to apply the block.

Traceability gaps made visible

We map which share of your sales can be traced to a customer and which carry batch or serial data, so you know before a recall whether you can contact buyers directly or will need a public notice, and what it would take to improve that.

People keep the decisions

Whether to recall, the wording of notices, the remedy offered and contact with regulators stay with your recall coordinator and advisers. Automation builds the lists, applies the blocks, sends approved messages and keeps the log.

From No Plan to a Rehearsed Recall

Five steps. Most businesses can reach a tested manual runbook in a few weeks, with automation added channel by channel where it is justified.

Inventory every sales channel

List every place a product can be sold, reserved or shipped: each store POS, websites, marketplaces, trade portals, subscriptions, warehouses and logistics partners, with who can block a product in each and how long it takes.

Assess traceability

Measure how many sales link to a known customer, whether batch or serial numbers reach the sale, and whether wholesale dispatches record the batch shipped to each retailer.

Write and test the runbook

A step by step recall procedure with owners, approved notice templates, regulator contact steps and a timed mock recall. This is valuable even if nothing is ever automated.

Automate the slowest steps

Usually the stop sale flag across channels, holding open orders and building the affected customer list. Each is tested against a live product that is safe to block and unblock.

Rehearse yearly and after changes

Run a mock recall at least annually and after any new channel, POS upgrade or replatform, because each of those can quietly break a recall path.

FAQ

What are a retailer’s obligations during a product recall in Australia?

In general terms, the business that supplies the product, which can include manufacturers, importers, wholesalers and retailers, must stop supplying it once a recall is underway and cooperate with the recall. Under the Australian Consumer Law, a supplier who conducts a voluntary recall of consumer goods must notify the ACCC within two days, and suppliers must report to the ACCC within two days of becoming aware that a consumer good was associated with a death, serious injury or serious illness. Food recalls are coordinated through Food Standards Australia New Zealand and state food authorities, and therapeutic goods through the TGA. This is a general summary only. Get legal advice for your situation.

How quickly can we stop selling a product across all channels?

With a single stop sale flag pushed to every channel through an integration, online channels can usually be blocked within minutes. Store registers depend on how your POS distributes item changes. Some update within seconds, others on a schedule, and some offline registers keep using cached data until they reconnect. Find out your actual propagation time for each channel and back up the system block with a direct message to store managers.

Can we find customers who bought in store without a loyalty card?

Usually not, if they paid by cash or card without giving any details. The POS records the sale but not the person. Sales linked to loyalty accounts, trade accounts, digital receipts or customer profiles can be traced. This is why a recall plan should measure what share of in store sales are linked to a customer, and why most recalls still include public notices in store, on the website and through the ACCC Product Safety Australia site.

Is it legal to use customer contact details to send recall notices?

Generally yes. Recall notices are typically a use of personal information the customer would reasonably expect for a purpose related to the sale, and there are also grounds relating to serious threats to health or safety. However, the recall list should be used only for the recall: no promotional content, no later reuse for marketing, and access limited to those running the recall. Check how the Australian Privacy Principles apply to your business with your adviser.

Do we need recall software or will our existing systems do?

Most retailers and wholesalers already have the raw capability in their existing systems: product blocking in the POS, unpublishing on the website, order history and customer records. What is usually missing is coordination: one action that applies the block everywhere, one list built from several sources and one log. That can often be added with integration rather than a separate recall platform. Very large or highly regulated businesses, such as food manufacturers supplying major chains, may also need dedicated recall and traceability tools.

What if we only track batches in the warehouse, not on sales?

Then plan for product level recalls, contacting every buyer of the product rather than only buyers of the affected batch. That is more disruptive but safer than guessing. If precise batch recalls matter for your category, such as food, cosmetics, baby products or electrical goods, the longer term fix is to carry the batch or serial number through dispatch and onto the sale record, which is covered on our batch, serial and expiry tracking page.

Should recall notices be sent automatically?

The list building and stop sale steps should be automatic and immediate. Sending notices should require explicit approval, because the wording, batch details and remedy must be correct and are often agreed with the supplier or manufacturer first. Once approved, the integration can send to every affected customer quickly, track delivery, flag bounced emails for follow up by SMS or post and log every message against the recall reference.

Be Ready to Pull a Product Before You Ever Need To

Book a call. We map every channel you sell through, show you how long a stop sale takes today and how many buyers you could actually reach, and give you a runbook and, only where it is justified, an automation plan. The assessment is yours either way.