Clarus shipments and batches
Lesson 11 of 28 5 min read
Import despatched goods outs from Clarus WMS for your account only, and read the batches and expiry dates the warehouse actually picked.
When the warehouse despatches a goods out, Supply Lens imports it as a Warehouse Shipment. For food, drink and health products, the batches picked matter as much as the quantities: they are what you need for traceability and recalls.
By the end of this lesson you will be able to import Clarus shipments for the right account and bring the picked batches with them.
Which shipments are imported
The Warehouse Shipment group has the standard import window (setupDate,
lastImportDate, importDelay) and one filter:
| filterByAccountCode | Imports only shipments held against this Clarus account. A Clarus site can hold several accounts, each a different supplier client, so set this to the organisation's own account code. Empty imports every account the credentials can see. |
|---|
Set the account code
On a shared warehouse, an empty account filter brings in other clients' despatches. Set it before the first live run.
Where the batch number lives
Clarus stores stock attributes in generic fields: five text attributes, string1 to
string5, and five date attributes, datetime1 to datetime5. Each Clarus account labels
these itself, so you need to tell Supply Lens which one holds the batch.
| batchNumberField | Which of string1 to string5 holds the batch number. Clarus labels string1 as the stock batch, which is usually the one to choose. Empty imports no batches. Empty by default. |
|---|---|
| batchExpiryField | Which of datetime1 to datetime5 holds the batch's expiry date. Leave empty if the warehouse does not record one. Empty by default. |
Each shipment line then carries the batches it was picked from, with the quantity picked from each, read from the stock the warehouse picked.
Stock with no batch
Stock with nothing in the batch field is not treated as a batch. A line picked only from such stock carries no batches.
Matching goods out and shipments
If you send batches on goods out (sendBatchNumbers), they go in string1 with expiry in
datetime2, the same attributes a goods in receipt books a batch under. If your warehouse
follows that convention, the natural choice on shipments is batchNumberField = string1
and batchExpiryField = datetime2. Confirm with the warehouse: the labels are per account.
Oakmoor Foods' recall readiness
Oakmoor's technical manager needs to know which customers received each batch. The
implementer asks the warehouse how it labels stock attributes and hears that the batch is in
string1 and the best-before date in datetime2. With those two settings, each shipment
line now arrives in Unleashed with the batches picked and the quantity from each.
Recap
- Warehouse Shipments use the standard import window and filterByAccountCode.
- Set the account code on a shared Clarus site.
- batchNumberField and batchExpiryField say which generic Clarus attributes hold the batch and expiry; both are empty by default.
- string1 is labelled as the stock batch by Clarus and is usually right, but confirm with the warehouse.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.