Skip to main content
The EAN (or GTIN) is a product barcode. The PCB indicates how many base units a package contains. In Bonx, a stockable unit is identified by the EAN + PCB pair. For example, a case of 6 and a case of 12 may share an EAN but have a different PCB. They are therefore two separate articles. Two articles may have the same EAN. They cannot have the same EAN + PCB pair.

​
Article data

The article record contains:
  • the EAN, used to identify the product in external exchanges;
  • the PCB, which gives the number of base units in one package.
Bonx quantities are expressed in packages. A quantity of 10 on an article with PCB 12 therefore means 10 cases, or 120 base units.

​
Articles with variants

The EAN and PCB are defined on each variant, because the variant holds the stock. They are not defined on the template article. Pack size can be a template attribute. Each value then creates a variant with its own EAN and PCB.

​
Use in flows

  • EDI: Bonx first searches by EAN + PCB, then by EAN alone, then by the supplier article code. It converts quantities between units and packages.
  • Document extraction: when several articles share an EAN and the PCB is missing, Bonx asks for validation instead of guessing.
  • Shopify: the barcode is synchronized with the EAN for each variant.

​
Current limitations

  • An article can have only one EAN. Unit and case EANs must be stored on separate articles.
  • Bonx does not validate the EAN check digit.
  • Bonx does not generate GS1 SSCC pallet codes.
  • The PCB is not copied to historical lines. Changing the article PCB does not recalculate old lines.
  • MRP uses the incremental order quantity. This is different from PCB and must be configured separately.