Warehouse configuration in xMatix is small on purpose: the flow itself — receive, allocate, pick, deliver, count — is fixed platform behavior, and what an administrator shapes is the master data and templates the flow runs on. This page lists what is configurable, where, and what deliberately is not.
Warehouse Settings: locations and lot types
The Warehouse Settings area holds the two warehouse master-data entities:
| Entity | What you configure |
|---|---|
| Storage locations | The branch's physical structure — locations, their types and hierarchy, the inventory flag, and the vehicle attributes for vans. Full field reference: Storage locations and vans. |
| Item lot types | The lot-tracking schemes items use — batch and serial behavior, described in Item lots and lot types. |
Document numbering
The warehouse documents — fulfilments, delivery orders, cycle counts, transfers and shipments — each have a document name setting that controls their automatic numbering. These are managed with the rest of the document numbering configuration in Setup; changing a setting affects documents created from then on.
Delivery checklist templates
The Populate Checklist action on a delivery order copies the lines of a checklist template of the Delivery type onto the document. You author the template: one line per check, each with a name, label and answer data type. With no Delivery template defined, the action creates nothing — silently, not with an error — so an empty checklist after running the action is a configuration finding, not a bug. Checklist templates of other types serve goods receipts, shipments and service orders the same way.
The van capacity check
A module setting controls whether van loads are checked against the vehicle's declared capacity at release:
| Mode | Behavior |
|---|---|
| Off | Loads release regardless of size. |
| Warn | An overload is flagged prominently on the transfer document, but the release proceeds. |
| Block | The release is refused until the load fits the declared limits. |
The check compares the planned load's total weight and volume — computed from unit weight/volume on the item master — against the van location's capacity weight (kg) and capacity volume (m³). Items missing unit weight or volume count as zero, and a van with neither capacity declared is never checked, so the setting is only as strict as the master data behind it.
What is not configurable here
- Posting rules. Which document lines post which stock movements is platform-managed configuration, viewable but not editable — see the inventory configuration reference.
- The action sequence. Allocate-before-pick, confirm-before-deliver, start-before-finish: these orderings are enforced by the platform, not by settings.
- Who may run what. Access to warehouse entities and their actions is granted per security profile; the custom actions (picking, release shipment, start counting, and the rest) each need an explicit action grant.
Common questions
Why does Populate Checklist do nothing for my users?
No checklist template of the Delivery type exists. Create the template with its lines and the action will copy them onto every delivery order it is run on. Because the action returns quietly rather than erroring, this is worth checking before any deeper investigation.
Can I change which movements post to the inventory ledger?
No — the posting rules ship as managed platform configuration, and the settings screen for them is read-only. If a posting behavior genuinely needs to differ for your organization, raise it through your implementation or support channel. The read-only screen remains useful diagnostically: it answers "why did this document post that movement".
Where do I configure counting rules?
On each cycle count document, not in a global setting: the scope filters (item, item group, ABC/FSN class, storage location, maximum items) and the count quantity type are per-count choices. See Cycle counting. What an administrator contributes globally is the classification data those filters select on — item classifications.