MASTER DATA
Catalog and compliance data that fails bad codes early.
Shape-driven products, unit normalization, MTO dimensions, and MX/US fiscal & transport profiles — locked when published so the dock doesn't discover errors.
What you get
The definitions every module shares.
- 01
Shape-driven specs
L/W/H, OD/ID, area, weight tracked dynamically.
- 02
MTO configurator
Dimensional customizability on quotes and orders.
- 03
Parties & fiscal profiles
RFC/CURP primitives and jurisdiction envelopes.
- 04
US tax/transport/customs profiles
Cross-border expansion without rebuilding Excel.
- 05
Packages as master data
How material is received and shipped.
- 06
Lifecycle locks on publish
Critical product and fiscal fields freeze when live.
Why master data is a plant risk
Bad SAT codes and fuzzy units poison shipments and invoices at the worst moment.
01
Industrial catalog, not retail SKUs
Sheets, tubes, rolls — geometry and weight the system understands.
02
Units without spreadsheet glue
Base, inventory, sale, purchase, and manufacture units with conversions.
03
Mexico-ready schemas
CFDI 4.0, Carta Porte 3.1, Comercio Exterior field shapes and SAT catalogs.
04
Honest PAC boundary
We own correct locked master data — stamping stays with your partner.
How clean master data reaches the dock
From catalog to validated document.
- 01DefineItems, variants, units, and packages.
- 02ValidateSAT and fiscal catalogs reject bad codes early.
- 03PublishLocks freeze the fields that must not drift.
- 04Use everywherePurchases, sales, portals, and AI share the same definitions.