Skip to content
Get in touch
00 — GuideWarehouseRev. 2 · 22.10.2026
  1. Insights
  2. Warehouse
GuideWarehouse

eExcise in the warehouse: what your WMS must handle

Receiving, storing, and dispatching marked goods under eExcise: which events to record, how to report them, and how to be ready for 1 July 2027.

Published
Updated
Reading
8 min
Language
UA · EN
Prepared by
Reticore Engineering
Contents
  1. 1.0What the warehouse is required to do
  2. 2.0A warehouse day under eExcise
  3. 3.0Mixed stock: two ledgers at once
  4. 4.0What the WMS must handle
  5. 5.0Two integration paths
  6. 6.0The bottom line

Most eExcise conversations focus on factories and checkouts. Between them sits the link that handles the lion’s share of daily operations with excisable goods — the warehouse. From 1 July 2027, every receiving, movement, and dispatch of marked product must be reflected in the state traceability system. For a warehouse that means one thing: either the WMS speaks eExcise, or people do — with everything that implies for speed and accuracy.

Status
Law 5013-IX is adopted and awaits the President’s signature.It moves mandatory eExcise to 1 July 2027. Until it takes effect — the day after publication — 1 November 2026 formally remains the date in force. Read the update

1.0What the warehouse is required to do#

The system’s logic is simple: the state wants to know where every marked unit is at any moment. So wholesale operators report the operations that change a product’s location or owner:

  • receiving from a producer, importer, or another distributor;
  • dispatching further down the chain — to a wholesaler or a retail point;
  • write-offs: breakage, loss, spoilage — the mark is retired from circulation;
  • returns to the supplier or from a customer.

Every movement is formalized as an excise electronic document (AED) signed with a qualified electronic signature — including transfers between one operator’s own warehouses. The system also automatically checks, among other things, that both parties to the document hold valid licenses. The AED must match physical reality: a gap between what left in the truck and what was declared in the system is no longer a bookkeeping error — it is a violation.

2.0A warehouse day under eExcise#

Receiving

A pallet arrives — expectation versus fact. The supplier declared a specific set of identifiers in the system; the warehouse must confirm those are what actually arrived. Aggregation decides everything here: if the pallet carries a unique group identifier (UGI) linked to every unit inside, receiving is one scan instead of a thousand. If not, someone scans every case or bottle.

Storage and stock

Stock now exists on two levels: the familiar SKU and quantity — and the list of concrete identifiers physically sitting in the bins. An inventory count under eExcise reconciles sets of codes, not counts.

Picking and dispatch

The outbound document carries the exact identifiers that went to the customer. That means scanning during picking: the system must know not that “40 cases shipped” but which 40 cases.

Write-offs

A broken bottle is not just minus one unit of stock — it is a mark that must be retired. A forgotten write-off surfaces later as a code the state considers alive that will never be sold.

3.0Mixed stock: two ledgers at once#

Until 31 December 2028 inclusive the warehouse lives in two regimes at once: goods with paper stamps (still legal to sell through) and goods with electronic marks. These are two different accounting circuits with different rules — and the WMS must tell them apart per line item, or eExcise reports will start including what they should not and missing what they should.

4.0What the WMS must handle#

  • stock accounting at the level of individual identifiers and group codes, not just SKUs;
  • scanning as part of every operation: receiving, transfers, picking, write-offs;
  • aggregation handling: pallet → case → unit, including breaking down and repacking;
  • expected-versus-actual reconciliation at receiving, with a discrepancy workflow;
  • building and signing eExcise reports without manual re-entry;
  • buffering reports through system outages with guaranteed delivery after recovery;
  • parallel paper and electronic accounting circuits until the end of 2028;
  • a log that shows the full history of any code that passed through the warehouse.

5.0Two integration paths#

  1. Exchange on the WMS side. The warehouse system builds and signs reports itself. Fewer moving parts and reporting stays closest to the physical operation; requires a WMS with native eExcise support.
  2. Exchange on the ERP or middleware side. The WMS records operations; a separate component reports them. Lets you keep a legacy WMS, but adds a synchronization point where the two ledgers can drift apart.

The right choice depends on how adaptable your WMS is and on who will own the discrepancies. Answer that question before July 2027, not after.

6.0The bottom line#

For a warehouse, eExcise is above all a precision requirement: every unit must be where it was reported to be. Our product ExciseTrace WMS was built around exactly that requirement — marked-goods accounting from receiving to dispatch, reporting to eExcise in real time. If your warehouse still runs on “we’ll count at month end”, the time left to change that habit runs out on 1 July 2027.

02 — End matter
Revisions
Revisions
Rev. 2Updated for Law 5013-IX
Rev. 1First published
03 — Read next
04 — Get in touch

Talk to the engineers who run eExcise in production.

ExciseTrace and ExciseTrace WMS report to eExcise from live factory lines and warehouses every day. If 1 July 2027 is on your calendar, write to us.