Support / Integrations
Connecting other systems
Getting released data into ERP and other business systems.
Released product data usually needs to reach other systems — ERP, MRP, a PLM-adjacent quality system, a web shop.
Common patterns
- Scheduled export. A command runs nightly and writes a file where the other system picks it up. Simple, robust, and easy to reason about when it goes wrong.
- Event-driven push. When an ECO releases, the changed lines are pushed immediately.
- Pull on request. The other system requests current data when it needs it.
What typically flows
| Direction | Data |
|---|---|
| Octagon → ERP | Released part masters, BOM structures, material and weight, supplier links |
| ERP → Octagon | Actual purchase costs, purchase order status, stock position |
Getting started
Field mapping is specific to your ERP and how it's configured. Talk to [email protected] and involve whoever administers the other system — the mapping conversation is the substance of the work.
One direction at a time
Start with releasing data outward. Two-way synchronisation is worth doing but it's a bigger commitment, and it's much easier once the one-way flow is proven.
Still stuck?
Email [email protected] and a person will pick it up. Include the part number and what you were doing — it saves a round trip.