Status: integration in progress. Everything on this page is available in the API; FHD’s own connector is being built against it.
Get the key
1
The company creates it
A company admin opens Settings → Integrations in BrandGate and uses the Fackhandelsdata tile (or the generic ERP or custom integration tile) to create a key (Generate API key) for the ERP vendor. It has the scopes an ERP integration needs.
2
The company sends it to FHD
The key is shown once. The company sends it to FHD through a safe channel. It only ever gives access to that one company, and the company can revoke it at any time.
3
Build against a test company first
Ask BrandGate for a test company and a test key through brandgate.dev/contact. Switch to the customer’s key at go-live.
What FHD does
Rules that keep it safe
- FHD owns product master data, prices, price lists, customer master data and delivery status. BrandGate owns orders, invoices, payments, images and customer logins. See who owns what.
- Every write is repeatable. Send an
Idempotency-Keyand your ownexternal_id; resending a batch never duplicates. - Store BrandGate’s order
idin FHD with a uniqueness rule, and look it up before creating an order, so a retry after a crash never creates a second order. See the integration model.
Go live
Use the go-live checklist.Connect it through the API
Building the connection yourself? These are the typical field matches. The steps are the same for every system: Build an ERP integration.Field names are the ones your ERP usually exposes; check them against your version. Amounts go to BrandGate as decimal strings with at most two decimals (
"299.50"), so round before you send: ERPs that hold prices as floating-point numbers need Math.round(x * 100) / 100.What the API cannot hold yet
- Customer discounts in percent and per-article discount agreements. Send the resulting absolute price in the customer’s price list.
- EAN and unit of measure.