How does HublerX know which label version is required for each customer and market?

The label version matrix is configured in HublerX by the regulatory and artwork team — mapping each SKU to the approved label version for each market or customer segment. The matrix is linked to the ERP customer master so that when a WO is created for a specific customer order, the required label version is retrieved automatically without any manual lookup.

Can HublerX handle markets where the same label is approved for multiple countries?

Yes. Label versions can be mapped to multiple markets — a single GCC label version approved for UAE, Saudi, Kuwait, and Oman, for example. Where a customer order ships to any of those markets, HublerX matches the order to the approved label version for the GCC market group, not individual country codes.

What if a label version expires or is withdrawn by the regulatory body?

Where a label version is withdrawn — regulatory revision, product reformulation, or incorrect declaration — the version is flagged as expired in the label matrix. Production runs that would use the expired version are blocked immediately. Existing finished goods stock carrying the expired label is flagged in the WMS for disposition — use-up where the market allows a grace period, or repack where it does not.

Can HublerX manage label version compliance for contract manufacturing or third-party packing?

Yes. Where a SKU is packed by a contract manufacturer or third-party packer, HublerX can share the label version requirement for each WO with the packing partner — via a portal or a structured file — and record the label version confirmation from the packer as part of the WO completion record. The compliance record is maintained in HublerX regardless of where packing occurs.

Label Compliance Management

HublerX manages label compliance across all markets and regulatory requirements — blocking production or dispatch of a SKU if the label version on the line has not been approved for the destination market, and tracking label version changes through the ECN process to prevent premature or missed cutover.