What Xero’s native inventory covers, and where it stops

Xero tracks inventory items, holds a quantity and a value, and posts the accounting correctly. Core Xero values stock on average cost (AVCO) rather than FIFO. That is not a shortcoming for most businesses: AVCO is an accepted method under UK GAAP (FRS 102) and for HMRC, so if your accountant has never raised it, it is almost certainly fine.

Where Xero stops is operational rather than financial. It has no native field for a lot number, batch code, serial number or expiry date in any tier. Core Xero holds a single stock pool, with no multi-warehouse or bin-level tracking. If you build or assemble what you sell, there is no bill of materials, no assemblies, no kitting and no manufacturing workflow. And there is no native multichannel inventory sync across Shopify, WooCommerce or Amazon.

The Inventory Plus question, and why your country matters

Xero sells its own paid inventory add-on, Xero Inventory Plus. It adds FIFO costing method selection and basic multi-location stock levels. It does not add lot numbers, batch codes, expiry dates or FEFO picking — that gap is present in core Xero and in Inventory Plus alike.

The qualification that matters most: as of mid-2026, Xero Inventory Plus is available in the US only, and in USD only. Rollout to other regions sits at “Gaining Support” on Xero’s own product ideas forum with no roadmap commitment. So if you run your business in Australia, New Zealand or the UK, the Xero-native upgrade path is not open to you at all — not even for FIFO costing or basic multi-location. For those markets, a third-party app is not one option among several. It is the only option.

What to look for in a Xero inventory app

Start from your gap, not from a feature list. Four questions settle most shortlists.

• Do you need traceability? Lot or batch numbers, expiry dates, and the ability to answer a recall or an audit. Xero cannot do this at any tier, so this gap always needs an app.
• Do you hold stock in more than one place? Core Xero gives you one pooled number.
• Do you build or assemble? Then you need bills of materials and production orders.
• Do you sell on more than one channel? Xero will not keep Shopify, WooCommerce or Amazon stock in step on its own.

Two practical checks beyond the feature list. Confirm the Xero sync is genuinely two-way, because a one-directional export leaves you reconciling by hand. And check whether traceability is included or sold separately, since that changes the real cost of closing the gap you came for.

The 8 best inventory apps for Xero: quick comparison

We keep specific prices off this page because they change, and several vendors have stopped publishing them. Check each vendor’s pricing page for current numbers.

Detailed reviews

1. Qoblex — best inventory management software for Xero overall

Qoblex syncs two-way with Xero, so Xero stays your book of record while Qoblex runs inventory, purchasing and orders. It closes the gaps Xero leaves at every tier: real per-location stock across multiple warehouses, multi-currency and multi-user support, demand forecasting rather than fixed reorder points, and a B2B wholesale store. It connects to Shopify and WooCommerce, with Amazon supported for inbound stock.

It is the strongest pick for Australian, New Zealand and UK businesses specifically, because Inventory Plus is not available to them and the native upgrade path is closed.

Two things to know before shortlisting. Lot, batch and expiry traceability is a paid add-on rather than part of the base product, so price it in if traceability is why you are looking. Manufacturing — bills of materials and production — sits on the Business tier and above.

Best for: small and mid-sized product businesses, especially in AU, NZ and the UK, that want traceability and multichannel control without taking on a mid-market ERP.

2. Unleashed — the established Xero-ecosystem choice

Unleashed is a mature platform with a long-standing presence in the Xero ecosystem and a dedicated Xero integration. It is a common shortlist entry for businesses that have outgrown spreadsheets and want something proven rather than something new.

Best for: established Xero users who want a mature platform and have the budget for it.

3. Cin7 Core — multichannel depth for mid-market

Cin7 Core, formerly sold as DEAR Inventory, is a capable mid-market platform with strong multichannel coverage. It carries setup and onboarding overhead that smaller teams often do not need, so it rewards businesses with the complexity and the implementation capacity to match it.

Best for: mid-market multichannel sellers who have outgrown SMB tooling.

4. Katana — visual production planning

Katana gives manufacturers a drag-and-drop production floor view with real-time inventory. If you think about your operation as a production schedule rather than a stock list, it reads more naturally than most of this list.

Best for: manufacturers who want production planning front and centre.

5. Finale Inventory — high-SKU and barcode workflows

Finale is most often shortlisted by warehouses carrying a lot of SKUs where barcode-driven picking and receiving is the daily reality. It is less of a manufacturing system than Katana.

Best for: high-SKU warehouses where barcode workflow is the priority.

6. inFlow — simple and affordable

inFlow keeps the feature set tight and the interface approachable, which suits small wholesalers who want stock control without a long implementation. It is lighter on manufacturing than Katana or Cin7 Core.

Best for: small wholesalers who value simplicity over depth.

7. Zoho Inventory — budget-friendly, especially inside Zoho

Zoho Inventory is the value pick, strongest when you already run other Zoho applications and want everything in one ecosystem. Outside that ecosystem the case is narrower.

Best for: budget-conscious teams already invested in Zoho.

8. Xero Inventory Plus — Xero’s own add-on

It belongs on this list honestly. If you are US-based, your gap is FIFO costing or basic multi-location stock, and you would rather not add another vendor, Inventory Plus is a legitimate answer and the simplest thing to try first. Staying inside Xero has real value.

Be clear about its limits before you choose it: it does not add lot numbers, batch codes, expiry dates or FEFO picking, and it is unavailable outside the US.

Best for: US-based Xero users whose gap is costing method or basic locations, not traceability.

Lot, batch and expiry tracking for Xero

This is the gap that sends most people looking, so it is worth stating precisely. Xero has no lot number, batch code or expiry date field in any tier of its product, and Xero Inventory Plus does not add them. Typing a batch code into a description does not make it traceable: you cannot filter, report or recall on it.

If you make or sell food, beverages, supplements or cosmetics, what you actually need is a lot number captured at receipt, an expiry date attached to that lot, stock visible by lot rather than as one pooled figure, picking that works oldest-expiry-first, and a report that answers “which customers received lot X” in minutes rather than days.

Qoblex adds that layer to Xero as a paid traceability add-on, with expiry flagged ahead of the date so stock can be worked through before it becomes a write-off. Unleashed, Cin7 Core, Katana and Finale also cover lot tracking. Any of them closes the gap; the question is how much platform you take on to get there.

How to choose

Match the pick to the gap. If traceability is the reason you are here, shortlist Qoblex, Unleashed and Cin7 Core, and price the traceability component specifically rather than comparing headline plans. If manufacturing is the driver, compare Katana and Cin7 Core on how they model production. If you are US-based and the gap is only costing method, try Inventory Plus before adding a vendor.

Whatever you shortlist, run one real workflow end to end during the trial: receive stock, allocate it, fulfil an order, and confirm it landed correctly in Xero. A demo shows the happy path. Your own messy order shows the truth.

When Xero’s native inventory is enough

Plenty of businesses need nothing on this page, and it is worth saying so plainly.

If you sell non-perishable products with no lot, batch or serial requirement, hold stock in one place, do not build or assemble what you sell, and sell through a single channel, Xero’s native inventory is genuinely sufficient. Its average-cost valuation is accepted practice, and a spreadsheet alongside Xero is how a lot of good businesses started. There is no need to add software before the workflow actually strains.

The signal that you have outgrown it is usually specific: a customer asks which batch they received, a second location opens, you start building products from components, or you add a sales channel and the stock numbers stop agreeing.

FAQ

What is the best inventory management software for Xero? Qoblex is our pick for most Xero users, followed by Unleashed, Cin7 Core, Katana, Finale Inventory, inFlow, Zoho Inventory and Xero Inventory Plus. Qoblex syncs two-way with Xero and adds multi-warehouse stock, purchasing, demand forecasting and lot and expiry traceability while Xero stays your book of record. The right pick depends on your gap: traceability, multi-location, manufacturing or multichannel.

Does Xero track lot numbers, batch codes or expiry dates? No. Xero has no native field for a lot number, batch code, serial number or expiry date in any tier, and Xero Inventory Plus does not add them either. Businesses that need batch traceability have to use a third-party inventory app. Typing a batch code into a description field does not make it traceable, because you cannot filter, report or recall on it.

Is Xero Inventory Plus available in Australia, New Zealand or the UK? No. As of mid-2026, Xero Inventory Plus is available in the US only and in USD only. Rollout to other regions sits at 'Gaining Support' on Xero's own product ideas forum with no roadmap commitment. If you are in Australia, New Zealand or the UK, the Xero-native upgrade path is not open to you, so a third-party app is the only route to FIFO costing, multi-location stock or traceability.

What does Xero Inventory Plus actually add? Xero Inventory Plus adds FIFO costing method selection and basic multi-location stock levels. It does not add lot numbers, batch codes, expiry dates or FEFO picking, and it does not add bills of materials or manufacturing. The traceability gap is present in core Xero and in Inventory Plus alike.

Does Xero support multi-warehouse inventory? Not in core Xero. Core Xero holds a single stock pool with no multi-warehouse or bin-level tracking. Xero Inventory Plus adds basic multi-location stock levels, but it is US-only. For a real per-location view outside the US, you need a third-party inventory app.

Does Xero use FIFO or average cost? Core Xero values stock on average cost (AVCO); FIFO is not available in core Xero. For most businesses that is fine — AVCO is an accepted method under UK GAAP (FRS 102) and for HMRC. If you specifically need FIFO, that is what Xero Inventory Plus adds, and that add-on is US-only.

Can Xero handle manufacturing or a bill of materials? No. Xero has no bill of materials, no assemblies, no kitting and no manufacturing workflow, and Inventory Plus does not add them. If you build or assemble what you sell, you need an inventory app that covers production.

Does an inventory app replace Xero? No, and it should not. The apps on this list sit alongside Xero and sync to it. Xero remains your accounting system and book of record while the inventory app runs stock, purchasing and fulfilment. Confirm the sync is two-way before you commit, because a one-directional export leaves you reconciling by hand.

When is Xero's built-in inventory enough? When you sell non-perishable products with no lot, batch or serial requirement, hold stock in a single location, do not build or assemble what you sell, and sell through one channel. Add software when the workflow strains — a customer asking which batch they received, a second location, or channel stock that stops agreeing.

You connected Shopify to QuickBooks because month end was taking three days. Orders now land in QuickBooks on their own, the payouts reconcile, and the three days are down to one. Then someone asks what the margin was on last month’s bestseller, and the answer takes an afternoon of spreadsheet work anyway.

That is not a broken integration. It is an integration doing exactly what it was built to do. A Shopify to QuickBooks connector moves the financial record: the order, the tax, the payout, the fees. It is an accounting pipe. What it does not move is the thing that actually determines your margin, which is what each unit cost you to get onto the shelf. If your connector is failing outright rather than working as designed, the troubleshooting guide covers that instead.

Where the gap actually sits

Three things fall through, and they fall through in the same order for most sellers.

Landed cost. The price on the supplier invoice is not what the unit cost you. Freight, duty, customs brokerage and the inspection you paid for in the origin country are all part of it. An accounting connector sees the Shopify order and the Shopify payout. It never sees the freight invoice that arrived six weeks after the purchase order, so the cost of goods it posts is the purchase price and nothing else. Your gross margin reads high, consistently, and nobody can say by how much. This is what landed cost tracking exists to fix.

Stock across more than one place. Shopify is always multi-location, even for a seller who thinks of themselves as having one warehouse. Add a 3PL, a trade-show van or a second stockroom and Shopify holds the quantities, but QuickBooks holds a single number for the item and no concept of where it is. The two agree on the total right up until they do not, and the reconciliation falls on whoever is closest.

Batches, expiry and serials. If your product has a date on it or a serial under it, neither Shopify nor QuickBooks records which batch went to which customer. When a supplier calls about a lot number, the honest answer from that stack is that you do not know, and you work it out from paper. Lot and batch tracking is the part that answers it.

What a stock layer in between does

Qoblex sits between the two rather than replacing either. Shopify stays the storefront. QuickBooks stays the book of record. The stock, the cost and the traceability live in the middle, where both of them can be fed from one set of numbers.

In practice that means the freight and duty on a shipment are spread across the units on it, so the cost that reaches QuickBooks is the landed cost rather than the invoice price. It means stock is held per location, and an order reserves the units the moment it is taken rather than at the point someone remembers to adjust. And it means a batch received on a purchase order is the same batch that leaves on a sales order, so a recall names customers instead of guessing at them.

None of that replaces the Shopify to QuickBooks connector you already have. It changes what that connector is carrying. The same shape applies to any storefront, which is why it also sits behind ecommerce inventory management generally.

When you do not need any of this

Plenty of Shopify sellers should stop reading here.

If you buy finished goods from a domestic supplier, pay one price with no freight line, hold everything in one room and sell nothing with a date on it, a direct Shopify to QuickBooks connector is the correct answer and a stock layer is an extra subscription doing nothing. The gap described above only opens when cost arrives separately from goods, or when stock exists in more than one place, or when units have to be individually identifiable.

When Katana is the better choice

Katana and Qoblex both sit in the same position between a storefront and an accounting system, and both handle bills of materials, production orders and batch tracking. The honest split is this.

Choose Katana if your constraint is the factory floor. If you need production scheduling, a shop-floor view for operators, or operator time captured against a job, Katana is built for that and Qoblex is not. Qoblex has production orders, bills of materials and costing; it does not have scheduling or shop-floor control, and its own manufacturing page says so rather than implying otherwise.

Choose Qoblex if your constraint is landed cost and selling in more than one way. If your goods come from overseas and the freight bill lands weeks after the stock, or you sell to trade accounts alongside a web store, the costing and the B2B side are where Qoblex is deeper.

One practical note on evaluating Katana. Katana no longer publishes paid pricing: its pricing page lists a free plan capped at 30 SKUs and a single custom-quoted “Advantage” plan on an annual contract (katanamrp.com/pricing, checked 13 October 2026). If you want a number before a sales call, you will have to ask for one.

How to decide in ten minutes

Answer three questions about last month.

1. Did any cost reach you after the goods did? Freight, duty, brokerage, inspection. If yes, your QuickBooks cost of goods is wrong and you do not know by how much.
2. Is your stock in more than one physical place, counting a 3PL or a van? If yes, one number in QuickBooks is not describing it.
3. Would you be able to name every customer who received a given batch, today, without opening a box file? If no, and your product has a date or a serial on it, that is a compliance exposure rather than an inconvenience.

One yes is worth a conversation. Three means the spreadsheet you are maintaining is already doing this job, badly, and someone is paying for it in hours.

FAQ

Does Qoblex replace my Shopify QuickBooks integration?

No. Shopify stays the storefront and QuickBooks stays the book of record. Qoblex holds the stock, the cost and the traceability in between and feeds both.

Does a Shopify QuickBooks connector handle landed cost?

No. It posts what Shopify tells it about the order and the payout. Freight and duty arrive on a separate invoice weeks later, and an accounting connector has no mechanism for attaching them to the units they belong to.

Can QuickBooks track inventory across multiple locations?

QuickBooks holds one quantity per item. Shopify is always multi-location. If you hold stock in more than one place, something has to reconcile the two, and today that is usually a person with a spreadsheet.

Is Katana or Qoblex better for a Shopify seller?

Katana if you need production scheduling or a shop-floor view. Qoblex if your costs arrive separately from your goods or you sell wholesale alongside the store. Both sit in the same place in the stack.

It usually starts with a count that doesn’t match. Someone walks the shelves with a clipboard and types the tally sheet in on Friday. Or a delivery gets shelved and three days later you find the supplier sent the 500 ml bottles instead of the 1 litre ones. Or a customer gets the blue variant when they ordered the grey. Each time, the fix that comes to mind is the same: we should be scanning barcodes. So you search for a scanner.

That instinct is right about the problem and often wrong about the first step. The clipboard was a reasonable way to run a small stockroom. It stops working when there are too many SKUs, counters, or orders for anyone to keep the numbers straight from memory. What fixes that is not the scanner in your hand. It is having somewhere for the scan to go.

What does “inventory software with a barcode scanner” actually mean?

Two searches hiding in one phrase

This phrase hides two questions. Which scanner should I buy? And which inventory system does something useful when I scan? That’s why the results mix marketplace listings, free apps, and software guides.

A barcode scanner on its own reads a barcode and turns it into text, the same characters you would type on a keyboard. A barcode inventory system is the software that takes that text, matches it to a product, and records what happened: this item arrived, was counted, was picked. You don’t need special software to make a scanner produce characters. You do need inventory software built around scanning if you want those characters to change your stock record.

What scanning changes

A scan matches a physical unit to a system record instantly, instead of someone reading a SKU off a box or copying it from a tally sheet later. Fewer steps between the shelf and the record means fewer places for a wrong digit to creep in.

Do you need to buy a barcode scanner first?

Usually not. Name the job you want to speed up, then check whether the devices you have can do it.

What a phone camera can do

In Qoblex’s mobile app, the phone camera is the scanner. It reads all common barcode formats, and you scan to find a product, add it to an order, or count it. The app runs on iPhone, iPad and Android, and the product page answers the question directly: “Do I need a barcode scanner? No.” The phone your team already carries is the hardware.

If you already own handheld scanners

Keep them. Scanners you already own work with the Qoblex web app on a desktop for receiving and recording supplier bills, and for stock counts: the guide to counting stock with scanners notes that most handheld scanners do the typing and submitting for you in the “Search by SKU or barcode” field. Any plug-and-play USB or Bluetooth barcode scanner works, because it types into the field the way a keyboard would. There is nothing Qoblex-specific to pair or configure.

When dedicated hardware earns its place

The good reasons to buy a dedicated scanner are about conditions, not software. If someone scans hundreds of items an hour, all day, a purpose-built device is faster and more comfortable than a phone. Gloves, cold rooms, and dusty or wet environments are harder on phones than on rugged handhelds. A fixed station at a packing bench makes sense once volume is steady. Qoblex doesn’t sell scanners or recommend a brand; our guide to choosing the right barcode scanner covers the hardware side.

What barcode scanning actually fixes in inventory management

Scanning improves accuracy in three places. If none of them hurt today, it will feel like overhead.

Receiving: scan against the purchase order

The expensive mistake at receiving is shelving the wrong item and finding out later. Scanning against the purchase order catches it at the door. In Qoblex, a purchase order has a With a Barcode Scanner option next to Receive: each scan is matched to an order line by barcode, capped at what is still outstanding, and Qoblex creates a draft goods receipt note (GRN) for you to review and authorize. Batch, lot, or serial details are captured in a Receive Batch dialog at that point, as with manual receiving.

You can then print product labels from a template, from the Products list or the GRN. With the template’s barcode setting on, the label carries a Code 128 barcode from the product’s barcode field, so items that arrived unlabelled can be scanned from then on.

Counting: scan the shelf where the shelf is

The tally sheet is where count errors live, because every number is written once and typed again. Scanning removes the second step: what you count is what gets recorded, with your name on it. On the desktop, the stock adjustment has a Scanner panel where each scan records a unit, with Add to build a running count and Set to state the total you counted, including zero for an empty shelf.

Picking: scan as you pick

Picking errors reach the customer, so they are the most visible of the three. Scanning as you pick catches the wrong variant before it goes in the box. The mobile app handles picking, packing and dispatch on the phone, and on the desktop the dropdown next to Ship offers a barcode option that builds the shipment from what you scan. Batch and serial tracked items get a dialog to record which ones were picked.

What proper barcode-driven inventory tracking actually requires

Whichever software you choose, these are the questions worth asking.

A live record the scan updates

The scan should change the real stock record straight away. If scans land in an app that uploads overnight, or a spreadsheet beside the real system, you’ve added a step instead of removing one.

A place for the scan at every stage

A lookup tool doesn’t fix much on its own. The scan needs to become a GRN line at receiving, a counted quantity at the count, and a shipment line at picking.

A record of who scanned what, and when

An updated total is not an audit trail. In Qoblex’s stock count, the Scan Log shows each Add or Set with its quantity, running total and time, and misses (a product not found, a scan error) collect under Missed Scans to work through before the count closes. Several people can count the same adjustment at once; each counter’s scans stay a separate record, and once a second person counts, the adjustment must be reconciled before it can be authorized. That answers “who counted this shelf?” without asking around.

The honest limit

Scanning a batch- or lot-tracked product during a stock count in Qoblex currently shows “Not Supported Yet” and records no count. Those products are counted by hand and the number is passed to whoever reconciles the adjustment. Receiving and picking still capture batch details as described above. If most of your catalogue is batch tracked and stocktakes are your main reason for scanning, know this going in.

How Qoblex uses barcode scanning

Qoblex sits between spreadsheets and a full ERP: the operational layer for inventory, purchasing, and fulfilment, while your existing tools keep their jobs. Scanning is how much of its data arrives.

The mobile app: the camera is the scanner

The mobile app covers the jobs away from a desk: sales orders, stocktakes and adjustments, picking, packing and dispatch, and looking up the price for the customer in front of you. It works against the live account, with the same permissions as the desktop.

The desktop web app: receive, ship, count

On the desktop, three workflows accept scans: receiving a purchase order, building a shipment, and counting a stock adjustment. Any plug-and-play USB or Bluetooth barcode scanner can drive all three.

One stock record, not a spreadsheet beside it

There is no separate mobile copy of your data. A scan updates the same Qoblex account the office uses, which is the point of keeping inventory control in one place. Xero or QuickBooks Online stays your books; Shopify or WooCommerce stays your storefront. For more than one site, warehouse management covers locations and pick and pack.

Who this is for

Small and growing teams with one or a few locations, a catalogue too big to count from memory, and regular receiving, counting, and picking. Especially teams on Xero, QuickBooks Online, Shopify, or WooCommerce whose stock number there no longer tells the truth.

Which method fits which job

When you don’t need barcode scanning at all

Scanning fixes a specific kind of mess. No mess, no need.

A handful of SKUs

If you carry twenty products and can see them all from where you stand, counting by eye and a stock figure next to your accounting software still tell the truth. A spreadsheet is enough while one person owns it and it matches the shelf. Change when it doesn’t.

A single shop where the till does the work

In a single-location store where stock only leaves through the point of sale and deliveries are small enough to check by eye, the POS already records sales. If no receiving, counting, or picking workflow is causing errors, a scanner adds a step without removing one.

You need more than a handheld can keep up with

At the other end, some operations outgrow handheld scanning: conveyor lines, pallets moving through dock doors, or counts that can’t depend on pointing a device at each item. There, fixed scanning or RFID is the right answer, and a different investment. Our guide to RFID inventory management covers when it makes sense.

What it costs

Scanning carries no separate charge in Qoblex. The mobile app is a paid add-on on the Starter and Business plans and included on Scale; current figures are on the pricing page. A scanner you already own costs nothing extra with the desktop app. A new dedicated scanner is a one-time hardware purchase outside any subscription; a phone the team already carries adds nothing.

It usually starts with a sale you type twice. The order comes in, you knock the item off the stock spreadsheet, then raise the same invoice in your accounting software. A delivery arrives, and you update the sheet and enter the supplier bill in the books. None of it is hard. It is the same fact recorded in two places by the same tired person, and at some point the two places stop agreeing.

So you go looking for one tool, one entry, one number. That is a reasonable thing to want. The honest answer depends on what you actually sell.

Do you need one tool, or two that talk to each other?

What people searching for “inventory and accounting software” are really asking

Almost nobody wants a bigger accounting system. They want to stop entering things twice, and to trust that the stock number and the money number agree. Two tools sharing one record automatically gets you that, without forcing one product to be good at two different jobs.

And they are different jobs. Accounting software is built around the general ledger; its inventory features exist so the ledger has a stock value and a cost of goods sold (COGS). Dedicated inventory software is built around the goods: which location, which batch, what they cost once freight is added, what to order or make next. One tracks stock for the books. The other tracks stock for the people moving it.

The short, honest answer: keep your books, add an inventory layer that syncs to them

For most small businesses holding real stock, the answer is two tools that talk to each other. Keep Xero or QuickBooks Online as the book of record, where your accountant works and your tax is filed from. Add an inventory system that owns the stock and posts the results into your books on its own. Your accounting software stays exactly where it is. If you are weighing a full ERP instead, our guide to enterprise resource planning covers that bigger decision; for many small teams it is more system than the problem needs.

What do Xero and QuickBooks Online actually do with inventory natively?

Both platforms have real, usable inventory tracking. The gap only makes sense once you know what that tracking covers, so start there.

Xero: tracked items, average cost, up to about 4,000 items

As of September 2026, Xero’s own inventory page describes real-time stock levels, up to about 4,000 items, and profitability by product. Core Xero values them at average cost (AVCO) only, with no FIFO (Jacrox, July 2026). The US-only Xero Inventory Plus add-on adds FIFO and basic multi-location (inFlow, July 2026). For a manageable range of finished goods, that is a solid base.

The same Xero page mentions no costing method, multiple locations, or lot tracking, and names Cin7 Core, Unleashed, and ZapInventory as apps to add for “greater automation over multiple sales channels.” Xero itself points this reader toward a dedicated app. More in our Xero inventory management guide.

QuickBooks Online: quantity, FIFO, reorder points, and purchase orders on Plus and Advanced

As of September 2026, Intuit’s pricing page shows inventory tracking, with quantity on hand, reorder points, and purchase orders, on the Plus and Advanced plans only. QBO values inventory using either FIFO, the default, or Moving Average Cost. The choice is made in settings before your first inventory item exists; create an item without choosing and QBO locks you into FIFO. There is no LIFO option. The QuickBooks inventory management guide maps every plan.

What both leave out

The gap sits in the same four places on both platforms.

• Landed cost. Neither has a native landed-cost allocation feature: Xero’s own product-ideas board carries an open, unroadmapped request to allocate freight and duty to inventory (Xero product ideas), and Intuit’s landed-cost help articles are scoped only to QuickBooks Desktop Enterprise, not QuickBooks Online. Either way, an importer’s margins run on a cost that is too low until freight and duty are added.
• Lot, batch, serial, and expiry tracking. Xero has no native field for any of them in any tier (inFlow, July 2026). QuickBooks Online has no native lot or batch tracking and no true serial tracing (Katana, July 2026; confirmed by Intuit); those live in QuickBooks Desktop Enterprise with Advanced Inventory, a separate product.
• Stock across several locations. Core Xero keeps one stock pool. QBO’s “location” field tags a transaction for reporting but holds no quantity per warehouse (Method, July 2026); true per-site quantity tracking is a QuickBooks Desktop Enterprise feature.
• Bills of materials and manufacturing. Xero has no bill of materials (BOM); its own product-ideas board shows the request still open and unroadmapped (Xero product ideas). QuickBooks Online has no native BOM, assembly, or production workflow; those live in QuickBooks Desktop and Desktop Enterprise (Digit, July 2026).

Xero, QuickBooks Online, and a synced inventory layer, side by side

Why does running inventory in a separate spreadsheet (or an unsynced app) backfire?

Spreadsheets next to the books are how many good businesses got going. The later trouble is structural, not a matter of discipline.

The double-entry problem: the same sale typed twice, and the two numbers drift

People call this double entry, though it has nothing to do with double-entry bookkeeping: every sale, delivery, and return recorded once in the stock sheet and once in the accounts. Each copy is a chance for a typo or a return that lands in one place and not the other. The drift is small, so nobody notices until a month-end when the two stock values disagree and nobody can say which is right. A second app that does not sync to your books does not fix this; it just gives the spreadsheet a nicer interface.

Tracking the same item as inventory in both places

The other trap catches people who do add an inventory app. If the product is also a tracked item in Xero or QuickBooks Online, both systems value it, each with its own method. The same sale produces two costs of goods sold, the stock value is counted twice, and the two never reconcile.

The fix is one owner for stock. The inventory system tracks quantity and cost and posts the value to your books as journals; the accounting platform treats the product as untracked, showing it on invoices without valuing it again.

What does a proper accounting and inventory sync look like?

“Integrates with Xero” can mean many things. A useful sync does three.

Stock value and COGS post to your books automatically, not as a month-end journal

When goods sell, COGS should reach your ledger on its own and your stock-on-hand balance should move with it. If someone calculates COGS in a spreadsheet and posts a month-end journal, the integration is skipping the part that matters.

Landed cost reaches unit cost before it reaches your margin report

Landed cost is the full cost of getting stock onto your shelf: supplier price plus freight, import duty, and handling. If the freight bill sits in an expense account while products are costed at supplier price, every margin on those goods flatters you. A good inventory system spreads freight and duty across the receipt, so unit cost is right before anything sells.

Sales orders become invoices, purchase orders become bills, refunds become credit notes

Your accountant’s documents should appear without retyping: an invoice when you sell, a bill when you buy, a credit note when you refund, and the payments. Channels such as a Shopify or WooCommerce store feed orders into the inventory system, which feeds the accounting.

How does Qoblex do this with Xero and QuickBooks Online?

This is the messy middle Qoblex is built for, between spreadsheets and a full ERP.

Qoblex is the operations layer; your accounting platform stays the book of record

Qoblex does not replace Xero or QuickBooks Online: your ledger, invoicing, bank reconciliation, and tax stay put. Qoblex owns stock, purchasing, and manufacturing, and syncs the results through its Xero integration or QuickBooks Online integration. Products sit in your accounting platform as untracked items, so they appear on invoices and bills while Qoblex stays the single source of stock value, which avoids the double-counting above.

What syncs, and how often

Qoblex posts sales invoices and their payments, credit notes for refunds, supplier bills and payments, and manufacturing costs into Xero or QuickBooks Online, on the ledger accounts you choose. Sales and purchase documents arrive within a few minutes of being authorized in Qoblex. The journals that post stock value and cost of goods sold run once a day, overnight.

What Qoblex adds beyond native tracking

• Landed cost. Freight, duty, and handling are spread across the received items by value, raising each unit cost as goods arrive.
• Costing. Moving average cost (MAC), the default, or FIFO, with COGS posted as orders are fulfilled.
• Lot, batch, serial, and expiry tracking. Captured at receiving, transfer, adjustment, and shipment, with expiring stock flagged; a paid add-on.
• Per-location stock. Each location holds its own count, with a bin number noting the shelf or bin the product sits in, and stock moves between locations on a transfer.
• Manufacturing. Multi-level bills of materials and production orders, what Qoblex calls MRP, on every plan.
• Purchase orders. The order, the goods received note (GRN), and the supplier bill sit on one record, so the three-way check is a screen, not an exercise.

When is your accounting platform’s built-in inventory enough?

A second system is not always the right call. Native inventory genuinely covers a lot of businesses.

You sell a modest, steady range from one location, with nothing to trace

If you sell a steady set of products from one stockroom, with no batches, serial numbers, or expiry dates to record, native tracking does the job. You need quantity on hand and a costing method, and both platforms provide them.

Your supplier costs are stable and you don’t import

If you buy locally and freight is small and predictable, there is no landed cost worth spreading. Average cost in Xero or FIFO in QBO gives a margin close enough to trust.

You don’t assemble or make anything

If everything you sell arrives finished, there is no bill of materials to maintain and no components to deduct, which removes one of the biggest reasons businesses outgrow accounting-only inventory.

You’re early, and a spreadsheet next to your books still tells the truth

If you are pre-revenue or in your first stretch of selling, with one or two people touching every order, a spreadsheet beside your accounting platform is a sensible setup, and adding a dedicated inventory app at that stage would be overkill. The signal to change is not a revenue number. It is the first time the sheet and the books disagree and nobody knows which is right, or the day a second location, an imported container, or a batch-coded product arrives.

What does it cost to add inventory software to Xero or QuickBooks Online?

How Qoblex pricing is shaped

Qoblex plans are set by order volume, and manufacturing is on every plan. On the smaller plans, each connection (one Xero or QuickBooks Online account, one Shopify or WooCommerce store) is a paid add-on, and lot, serial, and expiry tracking is a separate paid add-on; the largest plan includes both. Current figures are on the pricing page.

Any dedicated inventory app is a second line item

Whichever inventory app you choose, expect its own monthly cost on top of your accounting subscription. Xero’s and QuickBooks Online’s own native inventory tracking already comes bundled with your accounting plan; it is a dedicated inventory app closing the landed cost, lot tracking, and multi-location gaps that is priced separately, not included free. Compare it against the hours now spent re-entering sales and reconciling two stock numbers, not against zero.

FAQ

Most people search for pick and pack software the day after something went wrong. A customer found the blue one in the box instead of the black one. The packing slip listed six items and the box held four, because the order shipped in two parts. Or a retailer asked which batch a delivery came from, and the answer took an afternoon.

None of that means the team was careless. Picking from a printed order and a good memory works for a long time. It stops working when variants start to look alike, when orders leave in more than one shipment, and when some products need a record of exactly which unit went out.

What is pick and pack software?

Pick and pack is the part of fulfilment between “order confirmed” and “parcel gone.” The software gives that work a structure: it tells the picker what to collect, records what was packed, and marks the moment the goods leave.

Pick, pack, and the stage that actually matters: dispatch

Everyone names the first two stages. The third is the one that changes your numbers. Picking and packing are physical steps; dispatch is where the system records that stock has left the building.

What it produces: a pick list, a packing slip, and a label

A pick list tells a warehouse worker what to collect. A packing slip documents what is actually in the box. The pick list is an instruction; the packing slip is a record. A label goes on the outside of the box for whoever carries it.

Why do mis-picks and mismatched packing slips happen?

The wrong-item pick: reading instead of scanning

A picker working from a printed order is matching words on paper to products on a shelf. That breaks down with look-alike variants: the picker reads correctly and still grabs the neighbour. The fix is not “be more careful.” It is scanning the item, so the check happens against the barcode instead of someone’s eyes.

The packing slip that describes the order, not the box

An order for ten items arrives, seven are in stock, and seven go out today. If the slip is printed from the order, it lists all ten, and the customer emails you. The slip was right about the order and wrong about the shipment. Whenever orders ship in parts, the paperwork has to come from the shipment being sent.

No record of which batch or serial number left

For products with lot numbers, expiry dates or serial numbers, “we shipped 40 units” is not enough. Recalls, warranty claims and retailer audits ask which units. If nobody records the batch or serial while the item is in the picker’s hand, it gets reconstructed later from memory and delivery notes.

What should pick and pack software actually do?

The operator’s checklist:

• Print the pick list and packing slip from the shipment, not the order. That one design choice removes the mismatched-slip problem.
• Let the picker scan instead of read. Scanning at the shelf should catch the wrong variant before it’s boxed. For hardware, see our guide on choosing the right barcode scanner.
• Treat partial and multiple shipments as normal. Ship what is ready, leave the rest on the order, and ship again later, each shipment with its own carrier, tracking and dates.
• Record which batch or serial shipped, when the product needs it. For tracked products the pick shouldn’t complete until the units are recorded.

Here is how Qoblex answers each point.

How does Qoblex handle pick and pack?

Most pages that rank for this term are built for 3PL and high-volume shipping operations, or describe one feature inside a larger warehouse system. Qoblex is the inventory system that already holds your stock and sales orders, so pick and pack isn’t a separate app to keep in sync.

Pick, pack and dispatch as three shipment stages

You fulfil an order by creating a shipment for some or all of its lines. Per the shipments help article, the shipment moves through three stages, Pick, Pack and Dispatch. Dispatch is the one that reduces on-hand stock and commits cost of goods for the shipped units. If you don’t track picking and packing separately, you can dispatch directly.

Each shipment has its own ship-from location, carrier, tracking code and dates, and one order can have as many shipments as it needs. Pick lists, packing slips and labels print from the shipment, which is why a partial shipment’s slip matches the box. The sales order list also prints them in bulk. Allocating stock before shipping is optional, but recommended when stock is tight so the units you plan to ship are reserved.

Scanning in the web app, or with the phone camera

In the web app, the dropdown next to the Ship button has a barcode option. It opens a scanner, and the quantities you scan become the shipment lines, instead of lines you tick by hand.

On the mobile app, the phone’s camera is the scanner, so there’s no extra hardware. You work through the day’s shipments on the phone: pick, pack and dispatch. As the order management page puts it, scanning as you pick is what catches the wrong variant before it goes in the box rather than after it reaches the customer.

Batch and serial capture, and FEFO on expiring stock

When you pick a shipment containing batch- or serial-tracked products, Qoblex asks which batches or serials are going out before the pick can finish. Serial-tracked items get one entry per unit, and the batch quantities have to add up to the quantity shipped.

On lots with an expiry date, per the lot tracking page, Qoblex picks first-expired-first-out (FEFO), shows each batch’s expiry date while you pick, and lets you override the choice when an order needs a longer shelf life. FIFO ships the oldest stock received; FEFO ships the stock closest to its date. The full mechanics are in our FEFO picking guide.

One record, from pick through invoicing

Because the shipment lives on the sales order, there’s no second system to reconcile. Once a shipment is dispatched you can raise the invoice for the shipped lines from the same record, and Qoblex syncs the financial side to Xero or QuickBooks Online. The picker, the stock count and the books are looking at the same event.

Orders from every channel in one list

A pick list shouldn’t care where an order came from. Orders from Shopify, WooCommerce, wholesale and Amazon all become sales orders in Qoblex (sales imports and channel sync). The Amazon integration is inbound: orders and returns flow in, and Qoblex doesn’t push stock back out to Amazon.

For picking strategy itself (batch, zone or wave picking, and the KPIs behind them), see our complete guide to warehouse picking.

When don’t you need dedicated pick and pack software?

You ship a handful of orders a day from a small space

If one or two people pack every order, the shelves are within reach, and a printed order still gets it right, software won’t fix a problem you don’t have. The signal to watch isn’t volume on its own. It’s the first wrong-item complaint nobody can explain, or the first slip that didn’t match the box.

A 3PL already picks and packs for you

If a third-party logistics provider fulfils your orders, the picking happens in their warehouse on their systems. Your problem is knowing what they hold and what they shipped: inventory visibility, not pick and pack.

You sell one SKU, or products nobody could mix up

Scanning earns its keep when products look alike. If you sell one product, or a few obviously different ones, the wrong-item pick barely exists. Unless you need batch or serial records, a printed order is enough.

And at the other end

A large, multi-site distribution operation with dedicated warehouse staff, slotting rules and wave planning may need a full warehouse management system. Most growing operators sit in between: past the clipboard, nowhere near needing enterprise warehouse software. That messy middle is where pick and pack inside the inventory system makes the most sense.

What does pick and pack software cost?

In Qoblex, shipments, pick lists, packing slips, and multiple or partial shipments are part of every plan. Two things are paid add-ons on Starter and Business and included on Scale: the mobile app, which is where camera scanning lives, and lot, serial and expiry tracking, which covers batch and serial capture at pick and FEFO. Current figures are on the pricing page.

A 3PL platform or a single-purpose scanning app also carries a monthly cost, so compare total cost against how many systems you’ll keep in agreement.

You probably got here the same way most people do. A profit report looked off. Margin on a good seller read healthier than it should for a season in which your supplier raised prices twice. You opened the product, saw a number in the Cost per item field, decided it was not obviously wrong, and moved on. Then it happened on another SKU.

Nothing is broken. Shopify is doing what it documents itself as doing, which is narrower than most growing merchants assume, and the gap only surfaces months after the buying decision that caused it. For the wider picture of Shopify’s native inventory, see our Shopify inventory management guide. This page takes one line from it: the cost field.

Does Shopify update your product cost automatically?

No. It holds whatever you last typed.

Where the Cost per item field lives

Cost per item sits on the product itself, in the pricing section of a product or variant in your Shopify admin, next to price and compare-at price, per Shopify’s product pricing documentation. One product, one field, one value. Bigger catalogues use the bulk editor or the API, but the mechanism is the same: something outside Shopify decides the number, and someone types it in.

It is a static number, not a running average

Shopify’s own wording is worth reading slowly. “The Cost per item field contains static data, which means that the data in your profit reports is only relevant to a specific point in time,” per the Help Center’s profit reports documentation. The same page notes that Shopify reports profit only for products that had a cost recorded at the time they were sold.

Static is the operative word. The field is a stored value, not a calculation, and nothing inside Shopify watches your buying and adjusts it. The same page is candid about the consequence: when cost changes over time, its documented options are to run your financial reports in another business system such as an ERP or accounting system, to use a reporting app, or to calculate costs and profits manually.

What happens when you receive a purchase order at a new price

Nothing, unless you go and edit the field. Merchants in Shopify’s own community forum describe editing cost during purchase-order receiving and finding the product’s cost unchanged once the PO is received, because Shopify keeps one cost per variant: the last price paid.

So the one moment when you genuinely learn what a unit costs is the moment the number does not move.

Why do Shopify margin and profit reports drift when supplier prices change?

One field, two jobs it cannot both do

Start with what is not happening. Shopify is not running a costing method behind that field: no cost layers, no running average, no engine deciding which units you sold. There is the value you last entered, and reporting built on top of it.

Past orders keep the cost recorded when they sold, which sounds reassuring until you see the flip side: if the field was stale when those orders shipped, correcting it today does not repair the margin history already reported with the wrong number. And the stock you still hold has only that same field to describe it. Type in a new, higher price and it applies across existing stock, so margin reporting stays inaccurate until someone notices, as merchants in that community thread describe.

What this looks like for a multi-supplier seller

Say you buy the same SKU from two suppliers, or from one supplier across a rising market. Two prices, one bin, one storefront, plus whatever other channels run off that stock pool. Shopify can hold one of those numbers. Not the blend. The last price paid becomes the cost of everything, and your margin per order, your bestseller ranking by profit and your reorder decisions all sit on top of it. This is usually where a merchant starts keeping a parallel spreadsheet of real costs. Reasonable response, and it works right up until it is a month behind.

Does the Cost per item field include landed costs like freight and duties?

Not automatically. Freight, duty and brokerage are things you work out elsewhere and add into the same static number by hand.

Plenty of merchants do exactly that, and for a stable import lane it is fair enough. The catch is that the entry describes one shipment. The next container has different freight, and the field does not know. Our moving average cost calculator does that arithmetic on your figures.

Allocating those charges across the lines of a purchase order, so the cost lands on the right units, is its own subject, and it happens on the purchase order rather than in a product field.

How to get true, automatically-updating COGS for a Shopify store

What “true” means here

A true cost recalculates when stock arrives instead of waiting for you to remember. The test: after you receive a purchase order at a new price, does your reported cost change without anyone touching a field? App Store tools exist that report on cost and profit, and the distinction worth holding on to is whether a tool reports on the cost you maintain, or maintains the cost for you.

How this works in Qoblex on a Shopify purchase receipt

Qoblex recalculates when the goods land. Per Qoblex’s moving average cost documentation, the average cost of each inventory item in stock is re-calculated after receiving inventory purchase orders, and the cost of ending inventory and the cost of goods sold are set at that average.

A Shopify-shaped example. You hold 200 units bought at 8.00 and receive 300 more at 9.50. Shopify’s field, once someone updates it, reads 9.50 for all 500 units. The blended cost of what you hold is 8.90, and that is the figure Qoblex carries into COGS and margin the moment the receipt is posted. Run the calculator on your own two purchases.

Extra supplier charges belong in there too: Qoblex supports shipping and freight charges on a purchase order.

How the cost gets back to Shopify and to your accounting platform

Your storefront should show the corrected number, and your accountant should not have to hear about any of it. As Qoblex for Shopify documents, Qoblex syncs product details including cost to Shopify and updates stock levels as items sell, and it integrates with QuickBooks Online and Xero, which stay your book of record. Margin and COGS reporting lives in Qoblex’s reporting.

Shopify native versus Shopify with a costing layer

The wider capability, costing that recalculates across every purchase channel rather than one storefront, sits on Qoblex’s inventory costing page.

When is Shopify’s built-in Cost per item field enough?

It genuinely is enough for a lot of stores, and moving to something heavier before you need it is its own mistake.

One supplier, stable prices. If a SKU costs what it cost last year, a static field is an accurate field. Automation would recalculate its way to the same number.

Few enough SKUs that a manual update is a five-minute job. Thirty products, a quarterly price list, a bulk edit, done. Small process, not a broken one, and small processes are allowed to stay manual.

No need for per-purchase margin precision. Early-stage and side-project stores need to know roughly whether the maths works, not which receipt a unit came from. The free calculator, run by hand once a quarter, covers it.

The line to watch for is not a revenue number. It is the day you buy the same SKU at two prices and have to decide which one to type in. That has no right answer inside a single field, and your margin history absorbs the difference.

You ordered from an overseas supplier three months ago. The goods arrived, you counted them in, and Shopify’s Cost per item field still says what it said the day you created the product: the supplier’s unit price. Then the freight invoice landed. Two weeks later, the duty. Both went into Xero or QuickBooks Online as expenses, correct as accounting entries and completely absent from the number you read when you check a product’s margin.

For a long stretch that was reasonable: one supplier, a shipment a quarter, freight that barely moved. The gap between the price you paid and the cost that landed was small enough to ignore. Then the lanes changed, a second supplier came on, duty on your category moved. Now the margin looks fine and you no longer trust it.

This page stays on that one gap, picking up where our overview of Shopify inventory management (published 23 July 2026) touches on it briefly. It sits under Qoblex’s landed costs hub, which covers freight-and-duty capture across any purchase channel.

Why doesn’t Shopify’s Cost per item field capture your true landed cost?

Because it holds a price, not a record of what a receipt cost you.

What does Shopify’s native cost field actually track?

One number per variant: what you paid the supplier, stored until you change it. Buying domestically at a stable price, that is close enough to true.

The limit shows up at receiving. Per Shopify’s own purchase order documentation, a native Shopify PO carries products, quantities, cost, payment terms, and supplier details: no freight line, no duty line, no landed-cost calculation when the stock is received. Merchants in Shopify’s own community describe it as “one scalar per inventory item, no location dimension, no cost layers.”

Why doesn’t the cost update when a freight or duty invoice arrives after the goods do?

Because there is nothing for it to update. Cost per item is a standing value, not a history of receipts, so a cost that surfaces three weeks after the container has no receipt to attach to. Operators in that thread report the consequence: invoices that arrive after the goods have sold leave those margins misstated.

One merchant has publicly asked Shopify for a landed cost field in the purchase order receiving workflow (posted 11 July 2026), describing the existing field as “a single overwritable value with no historical tracking.”

What happened to landed cost tracking after Stocky’s shutdown?

For a slice of merchants this got harder recently.

What could Stocky do for purchase-order costing that native Shopify doesn’t?

Stocky was Shopify’s own purchasing and forecasting app, and the path some merchants leaned on for buying depth the admin does not carry: deeper purchase orders, forecasting, and, for those who set it up that way, spreading shared shipment costs across an order’s lines rather than parking them as a separate expense.

What’s left for freight and duty allocation now that Stocky is gone?

Per Shopify’s own transition guidance, Stocky is no longer available as of 31 August 2026, and it was delisted from the Shopify App Store on 2 February 2026. What remains is the native workflow: create an order, add products, quantities and cost, receive stock. No cost-layer update on receipt, no margin calculation. So the accurate description is not “no purchase orders.” It is basic purchase orders, with no landed-cost computation at receiving.

What does skipping landed cost tracking actually cost you?

Not a catastrophe. Something quieter: decisions made on numbers that lean the same way every time.

How do unallocated freight and duty distort your per-SKU margin?

Every shipment cost that never reaches a unit makes your COGS look lower and your margin look higher than it is. It never errs the other way, so pricing off that number means pricing off an optimistic one.

The second effect is mix. A bulky, low-value SKU absorbs far more shipping cost per unit than a small, high-value one in the same container. Unallocated, the light expensive product quietly subsidises the heavy cheap one, and the line you believe is your best margin may not be.

Why does this get worse on imported or tariff-affected inventory?

Duty is assessed as a proportion of declared value, and freight moves with lane, season, and carrier. On imported stock, freight, duty, insurance, and handling are a larger and far less predictable share of unit cost than on a domestic pallet. The bigger and choppier that share, the further the flat field drifts.

How do you distribute freight and duty across a Shopify purchase order?

Mechanically this is a solved problem. Shared shipment costs get spread across an order’s lines two ways: by value, proportional to what each line cost, or by quantity, divided across units. By value is the usual default, because it tracks how customs charges behave.

Where can you see the full breakdown and a worked example?

The mechanics live in two places we keep current: the landed cost calculator, which carries both methods and a worked example, and the guide to calculating landed cost. For a Shopify merchant the question is not how the arithmetic works, but where it runs, and whether the result reaches the system you read margin from.

How do you add landed cost tracking to Shopify without replacing it?

Three honest options, suited to different sizes of operation.

What do the spreadsheet and single-purpose-app options look like, and where do they fall short?

The spreadsheet is where almost everyone starts, and it is a legitimate answer. Export the PO lines, add the freight and duty totals, allocate, and you have a real landed unit cost. For a handful of POs a quarter, that may be all you need.

It thins out in four places: when the invoice arrives after the goods have sold; when one freight bill covers several purchase orders; when the bill is in a different currency from the PO; and, the quiet one, when the corrected number stays in the spreadsheet and never reaches the system where anyone reads margin.

Apps are the second option, and two different jobs get called landed cost on the Shopify App Store. Some are customer-facing: Zonos calculates duty and tax at checkout, so you can collect it from the shopper. Others are merchant-side: Landara allocates freight and duty into a landed unit cost per receipt, records it as a dated FIFO cost layer, and writes the updated cost back to the Shopify variant. Be clear which problem you are buying a fix for.

What does an operations layer add that a single-purpose app doesn’t?

Context. Allocation is one step inside a purchasing workflow that also holds the order, the supplier, the receipt, and the stock it creates. Run it there and the corrected cost is simply what the item costs from that point on. Run it in a separate tool and you have one more sync to trust.

How does Qoblex handle landed cost on Shopify purchase orders?

Qoblex is the operations layer here: purchasing and costing, while Shopify does what it is good at.

What happens when you receive a PO in Qoblex?

The allocation happens at receipt. Per our landed cost calculator page: “When you receive a purchase order in Qoblex, it distributes the landed costs such as freight and duties across the received units by value and folds them into the item’s moving average cost.” What that moving average does as new stock arrives at different prices is a separate subject, inventory costing.

Does it handle multi-currency freight bills and freight split across multiple POs?

Yes, and these are the two cases that break spreadsheets first. Per the Qoblex purchase orders page, Qoblex supports extra supplier charges such as shipping and freight, supports “freight bills that are related to one or multiple purchase orders,” and those bills “can be in a different currency than the purchase orders they are related to.” One forwarder invoice covering three POs, billed in a currency none of them used, is an ordinary week for an importer.

Does Qoblex replace Shopify, or does Shopify stay the storefront?

Shopify stays the storefront. Per the Qoblex Shopify integration page, Qoblex captures Shopify orders immediately, syncs stock levels back in real time, supports more than 200 currencies, and runs several Shopify stores from one dashboard. Shopify keeps checkout and point of sale, Xero or QuickBooks Online stays your book of record, and Qoblex gets the real cost into the number before anyone reads a margin off it. If you manufacture rather than only resell, the same question shows up in production costing, covered in our guide to food COGS and landed cost.

When is Shopify’s native cost tracking enough?

Often enough that this section matters. Adding a costing layer before you have a costing problem is only complexity you do not need yet.

Which Shopify sellers genuinely don’t need landed-cost allocation?

If you buy domestically from one supplier, pay no duty, and freight is a small, predictable line relative to product cost, the flat Cost per item field is honestly fine. Load it with your unit price plus your usual freight allowance and the error stays small, stable, and in the same direction on every SKU, so it will not change a pricing or range decision. Low volume points the same way: at a few POs a quarter, spreadsheet reconciliation is feasible.

When does a flat cost-per-item estimate stop being good enough?

Watch the signals, not the calendar. Freight and duty becoming a material and variable share of unit cost, usually when you start importing. More than one supplier or lane, so no single allowance fits every SKU. A tariff-exposed category where the rate moves. Invoices that arrive after the goods have sold. Enough SKUs and POs that reconciliation becomes a job rather than a task. And the operator’s own tell: someone has to remember which purchase orders were corrected by hand, because the system does not know.

With one or two of those true, an allowance in the cost field is still defensible. With four, the flat number has stopped being an estimate.

For the first year or two, a direct-to-consumer beauty brand runs fine on Shopify and a spreadsheet, or Shopify and Xero or QuickBooks. Orders come in, stock counts down, the accountant reconciles at month end. Then a moment arrives that the current setup has no answer for. A retail buyer asks for lot numbers on the delivery paperwork, and there is nowhere in Shopify those numbers live. A batch of serum ships without any record of which raw material lot it came from. Someone tries to pick the older stock first so it does not expire on the shelf, and realizes there is no expiry field to sort by. The question at that point is not “do I need software?” It is “which piece is actually missing, and does fixing it mean replacing everything I already run?” The answer to the second half is no.

What does Shopify not do for beauty brand inventory?

Shopify is a genuinely capable storefront. It tracks quantity on hand, supports multiple locations as separate quantity buckets, sends low-stock alerts, and keeps a basic cost figure for margin reporting. For a brand selling a handful of SKUs to consumers, that is often enough, and there is nothing wrong with running that way while it works.

The wall is not about quantity. It is about everything a beauty product carries beyond a quantity: the lot it was made in, the date it expires or the period it stays good after opening, and the supplier order it arrived on. Shopify does not natively track lot or batch numbers; as the Qoblex lot tracking page confirms, every unit of a variant is treated as identical. It has no expiry date field and no way to enforce first-expired-first-out picking. Its Locations feature tracks a quantity per location but does not segregate stock by lot, hold an expiry per location, or manage bins. And it has no native purchase order management for raising and receiving supplier orders.

The accounting layer does not close this gap either. Xero and QuickBooks Online hold the finances accurately, but neither natively tracks lot numbers or expiry dates, and neither enforces FEFO. That is not a fault in them; a general ledger is not built to know which lot of lip balm is sitting on which shelf. The missing piece is the operations layer in the middle, the part that connects the sales channel, the physical stock, and the accounting book so they agree with each other.

Does Shopify track lot numbers or expiry dates for cosmetics?

Lot tracking is usually the first hard requirement a growing beauty brand runs into, and it tends to arrive from outside. A retail buyer or a cosmetics-specialist 3PL will ask for lot numbers on the delivery documentation, because that is how their side traces and isolates stock if something goes wrong. A brand running on Shopify alone has no lot numbers to give them, because the storefront does not record lots at all.

The same gap bites internally the day a brand needs to trace a finished batch back to the ingredient lot it was made from, whether for a quality question, a supplier issue, or a recall. Without lot tracking, that trace is a manual reconstruction from emails, invoices, and memory, done under exactly the time pressure where memory fails. Lot tracking is what turns that from an afternoon of stress into a report. For the fuller treatment of this, see the piece on cosmetics batch traceability.

Can Shopify track expiry dates for cosmetics?

Shopify has no expiry date field on inventory, so a brand selling products with a minimum durability date, or managing shelf life against a Period After Opening symbol, has nowhere to record when stock goes off. That has two costs. The first is quiet and financial: older stock sits behind fresher stock, nobody sees it aging, and eventually it becomes a write-off. The second is a compliance exposure, because near-dated or expired product can ship without anything in the system flagging it.

The fix is an inventory layer that records an expiry (or a manufacture date and a PAO window that computes a proxy expiry) at the point stock is received, surfaces near-dated lots before they become a problem, and enforces FEFO so the oldest good stock is picked first. That is the difference between hoping the warehouse remembers and having the system enforce it. The dedicated guide to cosmetics expiry and PAO management covers how this works in practice.

Does Shopify have purchase order management?

A beauty brand buying finished goods from a co-manufacturer, or raw materials for in-house production, needs to raise supplier orders, track them against lead times, and receive stock in against them. Shopify has no native purchase order management, so most brands fill this gap with email and a spreadsheet. That works until it doesn’t: the incoming stock lives in one place and the inventory record lives in another, and the two only meet when someone manually reconciles them.

The more important loss is the lot number. When a PO is received against specific lots, the lot is captured at the moment stock lands, which is the only clean point to capture it. Without a PO module linked to the inventory system, that first traceability link never gets recorded, and everything downstream inherits the gap.

What does inventory software add to a Shopify beauty brand stack?

The point here is not that Shopify is bad. Shopify does its job: storefront, orders, and quantity-level stock. An inventory layer does a different job: lots, expiry, FEFO, purchase orders, and lot-level multi-location visibility. Two tools, two jobs. The table below shows what the stack covers with and without that second piece.

How does Qoblex integrate with Shopify for a beauty brand?

Once the gap is clear, the shape of the fix is simple. Qoblex sits between the storefront and the ledger as the operations layer. Orders placed on Shopify flow into Qoblex for fulfillment, lot-tracked picking, and inventory adjustment, and Shopify stays exactly what it is: the storefront and the customer-facing channel. On the finance side, Qoblex integrates two-way with QuickBooks Online and Xero, so the accounting platform remains the book of record for invoicing and reconciliation. Nothing gets replaced; the piece in the middle gets added.

What that operations layer holds, per the capabilities listed on the Qoblex lot tracking page, is the set of things Shopify and the accounting tools do not: full lot and serial traceability with recall-ready audit trails, FEFO-driven picking with automated expiry alerts and write-off tracking, purchasing and vendor workflows, support for one or many warehouses, one-click recall reports that identify affected batches and who received them, and traceable bills of materials that connect raw materials to finished goods. Lot, batch, serial, and expiry tracking is a paid add-on rather than part of the base plan; the pricing page has the current structure.

Shopify is not the only channel this works with. Qoblex also connects to WooCommerce, so a brand not on Shopify gets the same operations layer behind its store; the WooCommerce inventory management guide covers that setup. And to be clear about the boundary: Qoblex is not a Shopify replacement. It runs alongside Shopify, adding the inventory operations layer while the storefront keeps doing what it already does well.

When is Shopify enough for a beauty brand?

Adding an inventory system before you need one is its own kind of waste, so it is worth being honest about the stages where Shopify alone is genuinely enough.

The first is the very early-stage brand: under ten SKUs, a single location, direct-to-consumer only, with no retailer or 3PL asking for lot documentation and no product carrying meaningful expiry risk. Shopify’s built-in quantity tracking, low-stock alerts, and basic cost figure cover that situation completely. There is no gap to close yet.

The second is the brand with long-shelf-life products and no multi-location complexity. If everything you sell stays good well beyond thirty months and carries only a PAO symbol, and a single 3PL handles fulfillment and already tracks lot and expiry on your behalf, layering an inventory system on top mostly duplicates work someone else is already doing.

The third is closely related: some cosmetics-specialist 3PLs provide lot and expiry visibility in their own warehouse system, with reporting exports. If that already satisfies your retailers’ requirements and leaves you recall-ready, you may not need your own inventory layer yet.

The honest rule of thumb is this. The right time to add an inventory system is when the spreadsheet workaround starts costing more in time, errors, and stress than the software costs in money. Before that point, keep it simple. This page sits within the broader cosmetics inventory management software guide if you want to see where your brand fits across the full picture, including lot control software and Shopify lot and expiry tracking in more depth.

Frequently asked questions

If the traceability chain was maintained at the time you made those products, you have a fast answer. If it was not, you are about to spend days reconstructing it from delivery notes, production sheets, and shipping records that were never designed to be read backward. This guide is about building that chain so the answer stays fast, and about running the trace when the moment comes. None of this is meant to alarm. Most cosmetics brands never face a mandatory recall. But the same chain that makes a recall containable is also the audit trail that earns the trust of retailers and buyers who ask, reasonably, how you would handle one.

What does cosmetics batch traceability actually mean? (the four-stage chain)

Strip away the regulatory language and traceability is a chain of four linked records. Each stage answers a plain question and connects to the next, so a query at one end reaches all the way to the other. When people say a brand “has traceability,” they mean these four records exist, they are linked, and someone can read them in either direction without rebuilding anything by hand. Get the chain right and a recall becomes a lookup; get it wrong at any single stage and the whole thing breaks at the weakest link, usually the one you did not think mattered until you needed it.

Stage 1: Ingredient lot receipt: where does the traceability chain start?

Every delivery of a raw material, active ingredient, fragrance compound, colorant, or preservative gets an internal lot number the moment it arrives. That receiving record captures the supplier name, the supplier’s own lot or batch reference, the quantity received, the date, and any certificate of analysis attached to the shipment. This is the anchor point. If you do not assign and record a lot at receiving, nothing downstream can be traced, because there is no identifier to trace back to.

Fragrance and colorant lots deserve particular attention here, because they are among the most frequent triggers for cosmetics recalls (banned allergens turning up in fragrance compounds, non-approved colorants). Tracking them as distinct inputs, rather than folding them into a generic “raw materials” bucket, is what lets you isolate a problem to a single lot later instead of every batch that used any fragrance at all.

One boundary worth stating early: the inventory system captures and stores this receiving data. Whether the lot passes incoming verification and is cleared for use is a decision your quality function makes. The software records what arrived; it does not approve it.

Stage 2: Production batch record: how do ingredient lots link to output batches?

When you run a production batch, the record that ties everything together is the Batch Manufacturing Record, or BMR. This is the core traceability document: it links every ingredient lot you consumed to the finished-goods batch you produced. A complete BMR carries a unique production batch number, the date of manufacture, the quantity of each ingredient lot used (cross-referenced by its internal lot number from Stage 1), and the output batch or batches assigned.

The BMR is what makes the chain bi-directional. Read it one way and you go backward from a finished batch to every ingredient lot that went into it; read it the other way and you go forward from a single ingredient lot to every finished batch that used it. That second direction is the one a recall depends on, and it only exists if the link was captured at production time. You cannot reconstruct it credibly after the fact. This is where a bill of materials earns its place: when production runs on a BOM and production orders, the consumption of specific ingredient lots is recorded against the output batch as part of making it, not as separate paperwork afterward. The inventory system captures the operational data (which lots, which quantities, which output batch); the formal review and quality release of that record, the sign-off that says the batch is good to sell, is a quality function, not an inventory one.

Stage 3: Finished goods batch: what is the unit that reaches the customer?

The finished product gets its own finished-goods batch or lot number. In practice this is usually the number printed on the consumer packaging, because EU Regulation 1223/2009 requires a batch number on the label so a product can be positively identified through the supply chain, especially in a recall. That finished-goods batch links back to the production BMR, one-to-one or many-to-one depending on how you split a production run.

At this stage the QC status is recorded (on hold, or approved and released), and if labels, closures, or other packaging components are themselves a plausible recall trigger for your products, those packaging lots can be tracked here too. As before, the system holds the batch record; the release decision belongs to quality.

Stage 4: Distribution record: how does a batch link to the customer?

The last link connects the finished-goods batch to the people who received it. Every shipment is recorded against a specific batch number: which customer or distributor, which order, what quantity, on what date. This forward record is the difference between a targeted recall and a blanket one. With it, you contact only the accounts that received an affected batch. Without it, you cannot prove who did or did not get the product, and a market-wide withdrawal becomes the only defensible option.

Distributors carry their own version of this obligation: under EU Regulation 1223/2009, distributors keep batch identification records for three years from the date the batch was made available. If you sell through distribution, that record needs to exist somewhere in the chain, whether it is yours or theirs.

How do you run a cosmetics recall trace? (backward and forward trace)

Here is the section you come back to when it is not a drill. A recall trace is two moves: a backward trace that finds what you made with a suspect ingredient, and a forward trace that finds who has it. Both are lookups against the chain you built above. When good traceability is in place, the result is a targeted field correction rather than a full market withdrawal, which is the whole point.

Backward trace: from suspect ingredient lot to production batches

You start with one input: the suspect ingredient lot number. It comes from a supplier notification, an internal QC flag, or an adverse event report. The action is a single query against the batch records: find every production batch that consumed that lot number. The output is a list of production batch numbers.

That is the backward trace, and it answers one question: what did we make with this ingredient? In a well-maintained system the lookup takes seconds. Done by hand across paper BMRs or spreadsheet tabs, the same question can eat days, and every hour spent reconstructing is an hour the affected product stays in the market.

This is the capability Qoblex describes as “Recalls Made Easy”: identify the affected batches instantly, then see who received them, without scrambling or guessing. Qoblex sits at the inventory and traceability layer, holding the ingredient-lot to production-batch links so this lookup returns an answer rather than a research project. The workflow is what matters, though; the tool is one way to run it.

Forward trace: from production batches to finished goods to customers

The forward trace picks up the list of production batches from step one. First query: which finished-goods batches came from those production batches? Second query: which customer shipments included units from those finished-goods batches? The output is a targeted list of accounts, orders, and quantities. That list is the scope of your recall.

The forward trace answers the question that decides how big the event is: who has stock we need to retrieve or notify? With the list in hand, you quarantine any remaining on-hand stock from the affected batches so it cannot ship, and you document the full trail, from ingredient lot to BMR to finished batch to shipments. That trail is both your action list and your evidence that the recall was handled properly.

What does a mock recall drill involve for a cosmetics brand?

The only way to know the trace works is to run it before it is real. A mock recall is straightforward: pick a finished-goods batch at random, trace it backward to every ingredient lot it used, trace it forward to every customer shipment that received it, and time the exercise. If it takes more than two hours, the record chain has gaps, and those gaps are exactly what a real recall would expose at the worst possible moment. Run this drill once a year, and after any major change to your systems or process. It turns recall readiness from something you claim in a supplier questionnaire into something you have actually demonstrated. The workflow maps directly onto cosmetics; the pattern is worth borrowing from our write-up on recall readiness and mock recall.

What does EU 1223/2009 require for cosmetics batch traceability? (regulatory context)

Two frameworks shape traceability for most cosmetics brands, one European and one American. What follows is orientation, not legal advice: confirm your specific obligations with the relevant authority and a qualified regulatory advisor, because the details depend on your role in the supply chain and where you sell.

On the EU side, Regulation 1223/2009 sets out a few load-bearing requirements. Article 19 requires a batch number on every label so a product can be identified throughout the supply chain, which is the label-side half of the traceability chain described above. Article 10 requires the Responsible Person to maintain the Product Information File for ten years after the last batch is placed on the market, and Article 7 requires distributors to keep batch identification records for three years. Alongside the regulation, ISO 22716, the harmonized good manufacturing practice standard for cosmetics, describes the traceability chain at each stage, from raw materials through to customer delivery. ISO 22716 describes the chain; it does not require any particular piece of inventory software, and software cannot make a business “ISO 22716 certified.” Certification is an assessment of your operation, not your tools.

On the US side, MoCRA (the Modernization of Cosmetics Regulation Act, signed into law in December 2022) sets record and reporting duties. It requires serious adverse events to be reported to the FDA within 15 business days of receiving the information, with follow-up medical information received within a year submitted within 15 business days as well. For record retention, the same source describes six years for large businesses and three years for small businesses (defined as those with average gross annual US cosmetics sales under 1 million dollars over the prior three years). MoCRA also directs the FDA to establish good manufacturing practice requirements by rulemaking, and that rule is the vehicle likely to carry more specific traceability expectations; confirm its current published status with the FDA and a qualified regulatory advisor before treating any GMP requirement as final and in force.

What belongs in traceability software vs. what belongs in a QMS?

This is the distinction that saves buyers from two expensive mistakes: expecting an inventory system to do a quality system’s job, or skipping the quality system because the inventory system “already handles compliance.” Neither is true, and the line is clean once you see it.

An inventory and traceability system does the operational work of the chain. That means assigning lots at receiving, keeping BOM-linked production batch records that show which ingredient lots went into which finished batch, assigning finished-goods batch numbers, holding distribution records that connect batch to customer, running forward and backward traces, managing expiry and first-expired-first-out rotation, generating recall reports, storing an attached document such as a certificate of analysis against a lot record, and giving you visibility across locations. This is the layer Qoblex operates in.

A quality management system does something different. Batch release approval and QC sign-off, deviation management, corrective and preventive action (CAPA), preparation of the Cosmetic Product Safety Report (CPSR), safety assessments, adverse event reporting to the FDA or EU authorities, ingredient specification governance, and independent laboratory result management all live in a dedicated QMS or eQMS. These are decisions and approvals about quality, not records of physical movement.

To put it plainly: Qoblex is an inventory and traceability system, not a quality management system. It does not perform batch release approval, deviation management, CAPA, or independent QC sign-off. It does not prepare the CPSR, perform safety assessments, or submit regulatory notifications or adverse event reports to regulators. It can attach a certificate of analysis to a lot record as a file, but it does not author, verify, or certify it. If you need those quality-governance functions, and a growing cosmetics brand eventually will, they belong in a system built for them, running alongside your inventory layer rather than inside it.

Does every cosmetics brand need dedicated traceability software?

Not every brand needs this on day one. It is worth being honest about that rather than pretending the software is mandatory from your first product, because in a few situations a manual approach still holds.

The first is the very early-stage brand: fewer than ten SKUs, one supplier per ingredient, a single location, no retail customers yet. At that scale a manual BMR spreadsheet and a paper lot log can genuinely maintain the chain. The cost is your time, not money. The catch is that a spreadsheet-based chain tends to break the moment you add a second product line or supplier, and it breaks quietly, so you often do not notice until you try to run a trace.

The second is the pure reseller. If you buy only finished goods from a co-manufacturer and resell them, with no internal production, and the co-manufacturer holds the full BMR and provides finished-goods lot numbers on delivery, then the traceability obligation above the distribution-record level sits with them. You still need to know which customers received which batches, but you are not maintaining a production chain you do not have.

The third is the brand with very limited distribution, where all products sit on-shelf at a single retailer and that retailer holds the distribution records. In that narrow case, the distribution-record part of the obligation may already be satisfied by the retailer’s system.

The honest note to end on: growing brands outgrow all three conditions faster than they expect. A second product, a second retailer, a first wholesale account, and suddenly the manual chain that felt sufficient is the thing slowing down a trace. To see where this fits alongside the rest of the operation, our cosmetics inventory management software overview is the place to start, and the cosmetics expiry and PAO management guide covers the shelf-life side of the same records. The traceability mechanics here are close cousins of the GMP batch records supplements teams keep, and they rest on the same foundation of solid lot control software.

Frequently asked questions about cosmetics batch traceability

Picture the stock you are actually holding right now. A few pallets of serum in the main warehouse, a run of body lotion sitting at a 3PL, a batch of lip balm that came in three months ago and has not moved. You want the oldest stock to leave first, because the alternative is a write-off and a customer receiving something closer to the end of its life than it should be. That is a normal, reasonable goal. Cosmetics just make it harder than most categories, because there are two completely different date concepts on the packaging and they do not behave the same way in a warehouse.

Some of your products carry a printed best-before date. Most of them carry an open-jar symbol with a number of months next to it, and that number is a consumer instruction about how long the product stays good after someone opens the jar. It is not a warehouse date. Neither concept is intuitive to manage in a spreadsheet or a basic inventory tool, and conflating them is how near-dated stock quietly ages out in a location nobody was watching. This guide walks through both, and how an inventory system can act on each one.

What are the two expiry frameworks in cosmetics: minimum durability date vs. PAO?

Cosmetics inventory has two distinct expiry concepts, and most operators treat them as one. Under EU Regulation 1223/2009, a product’s shelf life determines which mark it carries. Products that keep for 30 months or less show a minimum durability date under Article 19(1)(c). Products that keep for longer than 30 months are exempt from that date and instead show a period-after-opening symbol under Article 19(1)(d). One of these is a warehouse date you can act on directly. The other is not. Getting the distinction right is the whole job.

This is orientation for inventory operators, not regulatory advice. Your regulatory advisor or responsible person owns the shelf-life determination for each product; what follows is about how to hold those dates in stock and pick against them.

What is the minimum durability date (DMD) and how does it work for inventory?

The minimum durability date is the closest thing cosmetics have to a classic expiry date. It applies to products with a shelf life of 30 months or less, it is shown by the hourglass symbol followed by “best before the end of” and a date, and it is a fixed calendar date set at manufacture. The manufacturer arrives at it through stability testing, not by product category. Some formulations tend toward shorter shelf life, for example certain preservative-free ranges or products with oxidation-sensitive actives, but the date comes from testing a specific formula in specific packaging, not from a rule about what type of product it is.

For inventory, this is the easy case. The date is real, fixed, and printed. You capture it at receiving, hold it against the lot, and use it directly for FEFO picking and expiry alerts. Standard dated-stock management applies. The one discipline that matters is capturing it accurately at intake, because everything downstream reads from that field. Do not assume which of your products fall under the 30-month line; that is a per-product determination you confirm with whoever owns your product data.

What is PAO (period after opening) and what does it mean for warehouse rotation?

Products that keep for longer than 30 months are exempt from the minimum durability date and instead display the period after opening, or PAO. It is the open-jar symbol with a number of months beside it, so “12M” means the product is intended to stay good for twelve months after a consumer first opens it. That definition is doing a lot of work, so it is worth being precise about what a PAO is not, from an inventory point of view.

A PAO is not a fixed calendar expiry date set at manufacture. It does not start counting until a consumer opens the product. And it cannot be applied directly as a FEFO rotation date in a warehouse full of unopened stock, because none of that clock has started. What a PAO actually is: a consumer safety instruction that the manufacturer derived from stability testing. That same testing also tells the manufacturer the maximum shelf life of the product before it is opened. That pre-opening maximum shelf life, not the open-jar number, is what your inventory system can work with.

Some products carry neither mark. The PAO requirement has exemptions: single-use or single-dose products; products in sealed containers that prevent contact between the product and the outside environment during use, such as pump dispensers and pressurized aerosols; and products where there is no risk of deterioration once opened. If a product is exempt and also keeps for more than 30 months, it may show no date and no open jar at all, which is its own thing to reconcile in your records.

How do you manage PAO-only products in a warehouse using the 30-month threshold?

Here is the question that actually stops people. A product carries no printed expiry date, only a “12M” open jar. How do you run FEFO on it? You cannot rotate on a clock that has not started.

The common industry approach is to build a proxy date from two pieces of information you can get. First, the manufacture date, which is usually encoded in the batch number or printed on the pack. Second, the manufacturer’s internal maximum shelf-life figure, the pre-opening period that their stability testing established and that underpins the PAO in the first place. Add the shelf-life period to the manufacture date and you have a proxy expiry date for the lot. If a body lotion shows a 12M PAO but the manufacturer determined a 36-month maximum shelf life from manufacture, you track the manufacture date on the lot, add 36 months, and that computed date becomes the FEFO rotation date for that lot.

The critical mistake to avoid is treating “12M” as if it were the shelf life and dating your stock twelve months from receiving. That would systematically understate how long unopened stock is actually good for and drive premature write-offs. Distributors and 3PLs handling multiple brands should ask suppliers for both the manufacture date and the maximum shelf-life period, and put that on the delivery documentation, so the proxy can be calculated consistently across every brand they hold.

How does FEFO picking for cosmetics work and why does it matter?

FEFO, first expired first out, is the operational best practice for any stock that carries a date. It is not named in EU Regulation 1223/2009 or any cosmetics rule; the regulation deals with batch identification and record-keeping, and FEFO is simply how a well-run warehouse acts on those records. It covers the short-shelf-life segment through the minimum durability date and, via the manufacture-date proxy, the long-shelf-life PAO segment as well.

The reason to bother is concrete. FEFO cuts write-offs by moving the oldest stock first, it keeps end-of-life product from reaching customers, and it makes recall isolation far simpler because you already know which lot is where. Mechanically it is straightforward: the expiry date (real or proxy) is recorded at receiving, the system prioritizes picks from the lot with the earliest date, and the picker sees the lot and its date on the pick list rather than guessing. For the general mechanics beyond the cosmetics case, see our deeper walkthrough of FEFO picking software. This page is the cosmetics-specific application, and it links up to the broader cosmetics inventory management software guide if you want the full operational picture.

How do expiry alerts catch near-dated stock before it becomes write-off?

Picking in the right order only helps if the stock is moving. When it is not, you want to know before the date passes, not after. Proactive expiry alerts do that: you set a threshold, say ninety days to expiry, and the system flags lots crossing it. For cosmetics this matters most on PAO-only products, where a lot can quietly reach its internal shelf-life limit without any printed date on the shelf to prompt anyone. Without system-level visibility, that is exactly the stock that becomes waste. Qoblex surfaces this directly, with automated expiry alerts and write-off tracking on the lot and expiry tracking side of the product, so near-dated lots raise their hand while there is still time to act.

How does multi-location expiry visibility prevent hidden write-offs?

Growth tends to add a second warehouse or a 3PL before it adds anything else, and a lot that expires in a 3PL is exactly as much a write-off as one expiring in your own building. Expiry visibility has to span every location at once, or the near-dated stock you are not looking at becomes the write-off you did not see coming. The point of tracking dates across locations is that “what is nearing expiry” is a single question with one answer, not a separate spreadsheet per site.

How does Qoblex handle cosmetics expiry and PAO tracking?

With the problem laid out, here is where Qoblex fits. It works in the two modes the packaging demands. For a product with a minimum durability date, you record the actual expiry date at receiving and the system uses it directly for FEFO and alerts. For a PAO-only product, you record the manufacture date at the lot level and, if you want, an internally calculated proxy expiry date, and that date drives the same FEFO rotation and alert logic. The confirmed capabilities on qoblex.com/lot-tracking/ are near-expiry visibility across all locations, FEFO-driven picking, automated expiry alerts and write-off tracking, and multi-warehouse support.

Qoblex tracks the dates you enter. It does not calculate PAO periods from formulation data, run stability testing, or author the shelf-life determination. That work belongs to your quality and regulatory function. The system stores and acts on what the operator records, which is the right division of labor.

Lot, batch, and expiry tracking is a paid add-on rather than part of the base plan; current plan structure and pricing live on qoblex.com/pricing/. Because Qoblex sits alongside your accounting platform and sales channels rather than replacing them, it fills the lot and expiry layer without touching your book of record.

When is a spreadsheet or basic inventory tool still sufficient for cosmetics?

Not every cosmetics operator needs dedicated software for this today, and it is worth being honest about who does not.

If you are a very early-stage brand with a single short-shelf-life product line, every product carries a minimum durability date, you are under roughly fifteen SKUs in one location, and you personally manage picking, a well-kept spreadsheet with a dated receipt column and a weekly expiry review can genuinely still work. The dates are all real and printed, and you can hold the whole picture in your head.

If your entire range is extremely shelf-stable, some high-alcohol fragrances and anhydrous products fall here, and no product realistically risks expiring before it sells, then FEFO buys you little. Rotation only pays off when something can go out of date on the shelf.

And if you are a 3PL or contract manufacturer whose clients supply all the lot and expiry data, and the brand already runs an inventory system that covers it, adding a second system just to hold the same dates creates duplication rather than control. Spreadsheets are not the enemy here; they helped these businesses get moving, and the point is that the problem this page describes is not yet painful enough to justify the tooling. It usually becomes painful when the SKU count climbs, a second location appears, or the mix of dated and PAO-only products grows past what one person can track by hand.

Frequently asked questions