Does the partner have to change systems?

No. They keep their system and send the order out of it. That is precisely the point of the interface — otherwise it would be a portal again, with somebody typing into it.

What happens on a retry?

Nothing duplicated. The partner's reference decides: if it is known, the existing order comes back, flagged as a duplicate. Retries can therefore be automated safely.

How does the partner learn which values are allowed?

From the reference endpoint. It serves the permitted order and shipping types, glass types, thicknesses and crate types in machine-readable form, so the partner's system can validate before sending.

Do different prices apply through the interface?

No. The order belongs to the same dealer account, so the same conditions and the same volume tier apply as in the portal. The interface is a second route to the same order, not a second pricing model.

What if a partner has no developers?

Then the dealer portal stays the route, and both exist side by side. The interface pays off from the point where a partner orders often enough that retyping becomes a job of its own.

Dealer API for window and glass orders

The short answer

A dealer interface takes orders exactly as the dealer portal does, only by machine. The partner keeps their own system, quotes and plans there, and sends the finished order through a documented interface instead of emailing a PDF or a spreadsheet.

What separates it from a file is that the interface checks what it accepts. A wrong glass type or an impermissible size surfaces on submission, not in production.

How it is built

Five properties without which it fails in daily use

What decides is not the feature list but the behaviour when something goes wrong.

One key per partner

Every dealer gets their own key. Orders through the interface therefore belong to the same account as orders from the portal — same prices, same volume tier, same history. When a key was last used is visible.

Idempotent intake

The partner assigns their own reference to each order. If the same reference arrives a second time — after a timeout, a retry or a failure on their side — the interface answers with the order that already exists instead of creating a second one. Duplicate orders from network trouble simply do not happen.

Permitted values as their own endpoint

Which order types, shipping methods, glass types, thicknesses, tempering types and crate types are allowed is served by the interface itself. The partner validates against it instead of maintaining a list that eventually goes stale.

Status readable

The state of every submitted order can be queried. The partner's system can inform their customer without anyone at the plant being asked.

Documentation inside the application

The description sits where the key is managed — not in a PDF describing the version from two years ago.

What it changes in the partner relationship

As long as orders arrive as files, every partner is a small manual process: open, check, transfer, query. That caps how many partners an office can carry — and it caps them regardless of how good the prices are.

Through an interface the number of partners scales with production rather than with the office. The partner, in turn, does not give up their own system, which in practice is the most common condition for closer cooperation.

What measurably changes: figures from daily operation How the calculation works: area, minimum area, volume tier

Common questions

Questions that keep coming up

Does the partner have to change systems?: No. They keep their system and send the order out of it. That is precisely the point of the interface — otherwise it would be a portal again, with somebody typing into it.
What happens on a retry?: Nothing duplicated. The partner's reference decides: if it is known, the existing order comes back, flagged as a duplicate. Retries can therefore be automated safely.
How does the partner learn which values are allowed?: From the reference endpoint. It serves the permitted order and shipping types, glass types, thicknesses and crate types in machine-readable form, so the partner's system can validate before sending.
Do different prices apply through the interface?: No. The order belongs to the same dealer account, so the same conditions and the same volume tier apply as in the portal. The interface is a second route to the same order, not a second pricing model.
What if a partner has no developers?: Then the dealer portal stays the route, and both exist side by side. The interface pays off from the point where a partner orders often enough that retyping becomes a job of its own.

Book a call

Tell us about your process

Two sentences are enough: what runs on spreadsheets, paper or shouting today. You get an assessment within 48 hours, not a brochure.

✓First call at no cost

✓Reply within 48 hours

✓Fixed price per release