Value-Added Work and Expiry, Under Control.
Labeling, repackaging, kitting and gift wrapping are tracked line by line and billed only from confirmed work. A nightly check sorts every LPN by days to expiry, so nothing expires unnoticed.
Four value-added services, billed from real work.
Each service runs as a VAS job with one line per LPN. When a line is confirmed, a permanent VAS event is written, and billing reads only from those events.
-
Labeling
Re-label LPNs with updated barcodes. Every line needs a barcode rescan before it can be confirmed.
-
Repackaging
Move goods into new outer packaging, tracked line by line against each LPN.
-
Kitting
Assemble components into kits. A new kit LPN is created with a balanced breakdown and build entry on the ledger.
-
Gift Wrapping
Wrap items for retail and e-commerce orders, with units completed and rejected recorded per line.
Jobs that start themselves.
A VAS job can be activated by the inbound or outbound flow, or created by a supervisor at any time. Each job moves through a fixed lifecycle with supervisor sign-off at the end.
How a VAS-Job Starts
After receiving Activated automatically when the GRN is issued.
Before dispatch Activated automatically at dispatch, when the GIN is issued.
Ad hoc Created by a supervisor whenever a customer asks.
Job Life-Cycle
- Draft
- Pending
- In-Progress
- Completed
A job can be cancelled at any stage before completion.
- Lines only confirm in progress
- A line can only be confirmed once its job has been formally started, so no work is billed early.
- Skipped units are free
- Skipped and rejected units are never written as VAS events and never billed.
- Priority levels
- Standard, Express and Urgent, shown on the mobile task queue.
- Rate per service
- Each customer contract can set its own rate per service type, with a general VAS rate as the fallback.
- 4
- Service types
- 3
- Ways a job starts
- 1
- Billing source: VAS events
Expiry caught days ahead, every night.
A background check sorts every LPN by days left to expiry and raises alerts for anything at risk. The near-expiry register can be filtered by bucket at any time.
-
0 days or less
Expired
A write-off is required with supervisor sign-off before the stock leaves the ledger.
-
1 to 7 days
Critical
Flagged for urgent attention on the dashboard.
-
8 to 30 days
Near Expiry
The customer is notified and the stock is highlighted in the customer portal.
-
Over 30 days
Acceptable
Monitored only, and listed in the register for planning.
Pair expiry buckets with FEFO picking so the earliest-expiring safe stock always ships first.
Write-offs your auditors can follow.
Expired stock is removed from the ledger by a supervisor-approved write-off. Each one leaves a permanent record that is never edited or deleted.
-
Expired stock only
A write-off is only allowed once the expiry date has passed. Single LPN or bulk write-off.
-
Supervisor sign-off
Every write-off needs a supervisor's approval, recorded against the write-off number.
-
Its own ledger account
Expired goods post to Expired Goods Void, kept separate from disposals so reports never mix the two.
-
Quarantine stays separate
Quarantined LPNs cannot be written off here. They are resolved through the quarantine workflow instead.