Connecting to the platform catalog and binding own goods via API

The platform provides its own ready catalog — about 100,000 product positions from leading manufacturers of panels, edges and fittings. Your factory connects to the catalog via API, binds its goods to ours and works with a ready base instead of building it from scratch.

What this gives your factory

A ready base of ~100,000 positions — panels (chipboard, MDF, fibreboard, acrylic, glass), edges (PVC, ABS, melamine), fittings from major manufacturers. Updated centrally.
No need to enter manually — most of the assortment is already described: sheet dimensions, thickness, decor, manufacturer, article number, images. The factory only binds its prices and stocks.
A unified decor dictionary — the client sees familiar names and manufacturer codes; easy to search through the catalog.
Edge-panel compatibilities are already described in the platform for most combinations — no manual configuration needed.

How the factory binds its goods to the catalog

After connecting via API, your accounting system sees our catalog. For each of your goods you specify:

Match to our position — your «Egger H1180 chipboard» is bound to our card with the same article number / decor. Mapping by article number, barcode, or internal ID — your choice.
Own prices — per m², per sheet, combined cutting, etc. You can set several price types for a single position (see 4 sales types).
Own stock — taken from your accounting system in real time. The client in their cabinet sees «in stock» only when there is real availability.
Own parameters — individual material settings: trims, cutting direction, service disables, combined-cutting prohibition — individually for your position (see Per-material individual settings).
Own paired edge — if you traditionally put a specific edge on a specific panel, the binding is preserved and offered to the client first.

If a needed position is missing from our catalog

The catalog is large but does not cover everything (a rare decor, a local manufacturer, a non-standard size). In that case the position is added in the factory’s admin panel — the Catalog section. Positions are added by mass-importing goods from an XLSX file — there is no manual creation of a single position in the admin panel.

Supported systems

API connection is the platform’s standard mechanism. What can be connected:

Any system with an open API (JSON / XML / SOAP) — connected per the platform documentation, usually 1–3 days of work.
Common accounting and inventory systems — the exchange is set up the same way, no dedicated connector needed.
In-house accounting — the platform is not tied to a specific program: the system only needs to send HTTP requests and parse JSON.

What is required for the connection

The platform exposes a universal HTTP API to the factory. From the factory’s side, the connection consists of three parts:

API access key — issued to the factory upon a request to the platform’s technical support. Used to authorize each call.
Documentation of the available methods — the list of actions you can invoke (catalog references, product search, reading and updating stocks, working with orders, clients, production). Delivered together with the key.
Implementation on the factory side — a separate module or service that, from your accounting system, constructs HTTP requests to the platform’s API. The development is done by your IT team or an external contractor. The platform is not tied to a specific stack — any environment that supports HTTP requests and JSON work fits.

Goods mapping, price format, synchronization frequency, error handling and retry policy are decided by the factory itself — they are part of the handler’s implementation on its side. The platform is responsible for a stable API and its documentation.

The connection request is made by the factory through technical support — after agreeing on the workflow, the platform team provides the key, documentation and assists with the pilot requests.