When a Recall Hits at 6 PM: Lot Tracking and Consumption Tax in Food and Pharma

The phone rings at 6:02 on a Friday. A supplier says a batch of raw material that arrived last month may be contaminated. Your quality lead has one question before she calls the customers: which finished products, in which warehouses, shipped on which invoices, came from that one lot?

If the answer lives in three spreadsheets and somebody's memory, that is a long night. If it lives in your core business system, where every inventory balance is tagged to a lot, it is a ten-minute export.

This is the real reason food and pharmaceutical companies in Japan care about lot tracking. It is not a warehouse nicety. It is the difference between a contained incident and a public recall. And the same records that save you in a recall feed your consumption-tax filing. This post is about why traceability and tax belong on the same core business system, and what changes when they do.

A scene you will recognize

Picture a mid-sized frozen-foods maker in Osaka, about eighty staff, supplying private-label ready meals to three supermarket chains. They run a decent operation. Finished goods move out on pallets. Invoices go out on time. Month-end close takes about six working days.

Then the supplier calls about that raw lot. The quality lead opens the inventory screen and types the lot number. Nothing ties it forward. She reads through manufacturing orders by hand, matches dates, calls the warehouse to walk the shelves. By Sunday she has a list. It covers 14 percent of a single month's shipments across two customers. Some of it has already been eaten.

Japan recalls roughly 700 to 800 food products every year, and the majority of recalls are initiated by the manufacturers themselves. A study of 791 recalls in Japan published in the MDPI journal Sustainability (Sustainability 2022, 14(13), 7863) found that 662, about 84 percent, in 2018 were manufacturer-initiated. Recalls are routine, not rare, and the cost of being slow is measured in shelf space and trust.

A year later, after lot records moved into a single core business system, the same call plays out differently. The quality lead types the lot number. The system shows every inventory balance that holds that lot, by product and location. She exports the affected lots to CSV and walks it to sales. The list is ready before the supplier finishes apologizing.

What lot tracking actually means here

A lot is a specific batch of a product, identified by a lot number and, when it matters, an expiry date and a manufactured date. In a serious core business system, lots are not free-text stickers. They are first-class records that inventory balances point to.

The product master carries three flags that decide whether a product is lot-managed. One says whether the product requires lot management. One carries a lot-number prefix. One says whether the product requires expiry management. If expiry management is on, the system will not let you create a lot without an expiry date, and it rejects any expiry date before the manufactured date or in the past. That single rule, enforced at write time, stops a tired operator from booking stock that already failed quality.

Lot numbers can be auto-generated. The default format combines the product code, the date in YYYYMMDD form, and a sequence number. The third lot of product code ABC created today becomes ABC-20260628-003. You can also type your own, as long as it is unique within the company and follows the allowed character set.

Each lot carries a lifecycle status with four values: ACTIVE, QUARANTINED, BLOCKED, and EXPIRED. ACTIVE means pickable. QUARANTINED and BLOCKED are quality holds, the states you flip to when a lot is under investigation but you are not yet sure it is bad. EXPIRED is what an expiry-driven lot becomes when the date passes. These statuses control whether a lot is pickable, which is the whole game in food and pharma. You do not ship what is quarantined.

A free-form notes field sits on every lot. Quality findings and supplier references go there, and when a recall lands, the notes are what the quality team reads first.

The hardest part, and the part that matters most under pressure, is the traceability link. Every inventory balance can reference a lot. The same lot can sit in many balances across many locations. The combination of product, location, and lot is unique, which means the system knows, for every quantity on every shelf, exactly which lot it belongs to. That is what turns a recall from a warehouse walk into a query.

Lot records cannot be deleted while they still hold positive inventory. The system refuses the delete if any balance references the lot with a quantity above zero, so you cannot accidentally erase the audit trail while the stock still exists.

Why expiry management is the real margin killer

In food and pharma, expired stock is not just a compliance problem. It is written-off money. The discipline that keeps it from expiring on the shelf is first-expiry-first-out picking, known as FEFO.

A core business system that stores the expiry date on every lot is the precondition for FEFO. Without that date in a queryable field, the warehouse picks by habit, by what is in front, or by what arrived last. With it, the pick list can be ordered so the lot that expires soonest ships first.

Lot status reinforces this. Once a lot crosses into EXPIRED, it stops being pickable. The warehouse cannot pull it into a shipment if the system governs the pick. That forces expired stock into a review queue instead of into a customer's box. For a pharmaceutical distributor the same logic protects against shipping past a use-by date; for a supplements maker, against shipping product whose active potency has fallen off. The outcome is the same every time: less write-off, fewer chargebacks, fewer apologies.

The tax half of the same record

Here is the part most teams miss. The very same lots that drive a recall also drive the consumption tax on the sale. When the Osaka frozen-foods maker ships a finished lot, the shipment becomes a sales invoice carrying consumption tax. When the raw lot arrives, the supplier's bill becomes a purchase carrying input tax the company wants to credit.

Japan's qualified invoice system, in force since October 2023, made this unforgiving. To claim an input tax credit on a purchase, a business needs a qualified invoice from a registered issuer, carrying that issuer's registration number. The National Tax Agency reported 4,268,910, about 4.27 million, qualified invoice issuers registered by the end of 2023, and individual consumption-tax filings for fiscal 2023 jumped about 920,000 to around 1.97 million as formerly exempt businesses became taxpayers. The tax tail is now long, and it touches every lot that moves.

A core business system that treats tax as an afterthought, a flat 10 percent on every line, breaks at this point. Food and pharma deal with mixed rates constantly: reduced-rate food at 8 percent, standard consumables at 10 percent, tax-exempt exports, zero-rated ingredients. A flat-rate setup forces the accounting team to recompute everything by hand at month-end, exactly when nobody has time.

The fix is a tax-settings master that separates output tax from input tax at the account level. Each tax rate you define links to two accounts on the chart of accounts: a sales-tax liability account for output tax, and a purchase-tax asset account for input tax. The system validates this at write time. If you try to link a sales tax to an account that is not a liability account, it rejects the entry. If you try to link a purchase tax to an account that is not an asset account, it rejects the entry. You cannot accidentally post input tax to the wrong side of the ledger.

That separation is what makes the input-tax credit defensible. When the auditor asks which purchases generated which credits, the records sit on the correct accounts, tied to the correct rates, on the correct invoices. The qualified-invoice registration numbers that validate the credit live on the partner master, so an invoice that comes in already knows whether the issuer is registered.

This is the plumbing that decides whether month-end takes six days or sixteen.

The intersection: where traceability and tax meet

Put the two halves together. A recall pulls affected lots out of inventory. Those lots may have been sold, which means they already generated sales invoices with consumption tax. Some may need to be credited back. The raw material that caused the recall arrived on a purchase with input tax already claimed.

If traceability and tax live on the same core business system, these movements share one source of truth. The lot that ships drives the invoice that drives the tax. The lot that gets scrapped drives the inventory adjustment. When the recall is over, the audit trail is coherent, not three reconciliations stitched together. This matters most for the qualified-invoice regime, because credits depend on documents that match reality. A credit note that references a real lot, on a real invoice, tied to a real shipment, survives review. One typed from memory costs you later.

An honest look at what is manual today

A trustworthy system tells you where the automation stops. Three things in this workflow are not yet hands-off, and a serious vendor will say so plainly.

First, when a lot is scrapped or written off, that movement does not automatically post a journal entry to the general ledger. Scrap correctly reduces the stock balance. The matching accounting entry, the loss to a write-off account, is a manual journal today. The same holds for inventory valuation adjustments. This is on the roadmap, not automated now.

Second, there is no dedicated immutable audit-log table. What you have instead is audit discipline baked into the records themselves. Every tax setting carries who created it, who last updated it, and when; every lot carries creation and update timestamps. Approval workflows capture their own history, with the approver and timestamp on every step. For most internal-control purposes that is enough, but it is not a single append-only ledger, and you should not let anyone tell you it is.

Third, there is no multi-currency or exchange-rate engine. If you import raw material in dollars or euros, the yen conversion for the consumption-tax calculation is handled outside the system today. For a Japan-centric food or pharma operation this is rarely a blocker, but for an importer with heavy foreign-currency purchasing it is a real limit.

Honesty here is not a weakness. It is the difference between a system you trust to run a recall and one you stop trusting the first time it surprises you.

What changes for the company

After the move, month-end close drops from six days to three. The quality lead answers a recall question in minutes instead of a weekend. The accounting team files the consumption-tax return with input credits that map cleanly to purchases, because every rate sits on the correct account. Expired write-offs shrink, because FEFO picks the right lot first.

These are not hypothetical gains. They are the predictable consequence of putting traceability and tax on one core business system instead of three.

A note on cost and switching risk, where these conversations stall. Small and medium enterprises make up 99.7 percent of all enterprises in Japan, per METI data. For those companies, a core business system that charges per seat and demands a multi-month implementation is the wrong shape. The shape that fits lets you start with the modules you feel the pain of today, lot tracking, tax settings, invoicing, and add the rest as the business is ready. Each company keeps its data fully isolated, and access is granted by role, so the quality team sees lots and the accounting team sees tax, and neither stumbles into the other's records.

Frequently Asked Questions

We already track lots in spreadsheets. Why move?

Spreadsheets track lots. They do not link lots to inventory balances, to invoices, or to consumption-tax accounts. The value is not in recording the lot number. It is in the query that runs in a recall and the credit that posts cleanly at month-end. If your spreadsheet cannot answer which customers received a given lot in ten minutes, it is costing you risk you cannot see.

Will switching disrupt the warehouse during peak season?

It does not have to. A modular core business system like Kikan System lets you bring lot tracking and tax online first, while purchase orders and shipments continue on the old flow until the team is ready. The lot statuses (ACTIVE, QUARANTINED, BLOCKED, EXPIRED) and the write-time validation on expiry dates mean operators learn the rules by getting blocked at the moment of error, not by reading a manual. You can pilot this with a small team on the free plan covering up to 2 users, no credit card required.

Is the audit trail good enough for our internal controls?

For most reviews, yes. Every tax record carries the creator, the last updater, and timestamps, and every lot carries creation and update timestamps, while approval workflows capture the approver and time on each step. What is absent today is a dedicated immutable audit-log table. If your auditors require that specific artifact, plan for it as a roadmap item, not an out-of-the-box feature.

How does FEFO picking reduce expired-stock write-offs?

First-expiry-first-out picking works only when the expiry date is a queryable field on every lot, which is exactly how the lot records are structured. The pick list can be ordered so the lot that expires soonest ships first, and once a lot crosses into EXPIRED status it stops being pickable. That keeps expired stock out of customer shipments and forces it into a review queue instead, which directly cuts write-offs and chargebacks.

Key takeaway: food and pharma makers do not need a bigger system. They need one core business system where the lot that ships, the invoice it generates, and the consumption tax it carries all live on the same record.

Start with the records that protect you

If a 6 PM call about a contaminated lot keeps you up, the fix is not more spreadsheets. It is a core business system where lot traceability and separated consumption-tax accounts are first-class, validated, and connected.

Kikan System is built for this. Lot management with expiry-driven FEFO picking, four-state quality holds, and inventory balances tagged to every lot. Tax settings that separate output tax from input tax at the account level, with write-time validation and qualified-invoice registration numbers on the partner master.

Start free with up to 2 users, no credit card required, at /#get-started. See the plans at /#pricing. Run one recall drill on your own data before peak season lands. That is the test that tells you whether the system is real.