EDI with Ambient: what happens in the supplier's operations once the order arrives

Ambient and connecting suppliers by EDI

Ambient is a Romanian DIY, building materials and home-improvement retailer, founded in 1993 in Sibiu. It has stores in Sibiu, Bistrița, Mediaș, Sighișoara, Alba Iulia, Deva, Râmnicu Vâlcea and Târgu Mureș, a logistics centre in Sibiu and an online store. Ambient uses the Azuvio platform and is moving its supplier replenishment flow to EDI: phase one, started in November 2026, covers about 150 suppliers, with more joining in later phases. For you as a supplier the change is not only the document format: orders, deliveries and invoices to Ambient have to come from the same data your warehouse works with.

Ambient at a glance, as an EDI partner

The details below are valid as of 5 November 2026.

Retailer

Ambient: DIY, building materials and home improvement; founded 1993, Sibiu

Locations

8 stores in Transylvania and nearby, a logistics centre in Sibiu, an online store

EDI platform

Azuvio, the EDIconnect module of CRMconnect

Phase one

From November 2026, about 150 suppliers; further phases follow

Active documents

Order (ORDERS), dispatch advice (DESADV), receiving advice (RECADV), invoice (INVOIC)

From December 2026

Return order, correction / storno invoice

Location identifiers

One GLN (ILN) per location; the full list is below

EDI documents active with Ambient

Four documents flow between Ambient and its suppliers today. For each one, what matters on your side is where you receive it or what you generate it from.

What happens on your side once the Ambient order arrives

The same path for every order, from ORDERS to invoice. The operator steps in only where the data does not match.

1. 1

   ORDERSThe order lands in CRMconnect / OMS

   The Ambient order shows up in the order list next to orders from other channels. Items are matched to your codes, stock is reserved and the delivery location comes from the GLN. If you run an ERP, the order also reaches it through the ERP connector.

2. 2

   WMSPicking and dispatch in the warehouse

   The order becomes a picking task in the WMS. What is scanned during picking is what leaves: if an item is missing, the partial delivery is visible before loading, not at Ambient's receiving dock.

3. 3

   DESADVThe dispatch advice is built from shipping data

   When the shipment is closed, CRMconnect generates the DESADV with the order reference, the location GLN and the loaded quantities, and sends it through EDIconnect.

4. 4

   RECADVThe receipt is compared with the delivery

   When Ambient sends the receiving advice, each line is compared with the DESADV. Matching lines are closed; differences become a task for the person who handles the Ambient account.

5. 5

   INVOICThe invoice is checked before it goes out

   The invoice is issued in CRMconnect or in the ERP and checked against the order, the advice and the receipt. Prices come from the order, quantities from the delivery; a mismatch holds the invoice until someone reviews it.

What is added from December 2026

From December 2026, two situations that are usually handled by email or on paper today move to EDI as well.

• Return order

  Ambient announces the goods it is returning by EDI. In CRMconnect the document becomes a return linked to the Ambient customer, and the goods can be received into the warehouse against that return.

• Correction / storno invoice

  Corrections after invoicing (accepted receipt differences, returns, wrong prices) are sent as an EDI document referencing the original invoice, instead of being handled separately.

GLN (ILN) codes of Ambient locations

Ambient's locations, with the internal store code and the GLN (ILN type) used in EDI documents. Identifier type: ILN.

In ORDERS, DESADV and INVOIC, use the GLN of the delivery location exactly as it appears in the Ambient order. The head office, the Sibiu store, the logistics centre and the online store share the same GLN (2008892534120), so the location is never inferred from its name: it is taken from the order.

With or without an ERP

If you have an ERP, CRMconnect works alongside it: Ambient orders are visible in the ERP too, the invoice can be issued from the ERP, and accounting stays there. CRMconnect handles the operational part: the order, the warehouse, the dispatch advice and receipt reconciliation. If you have no ERP, the whole flow runs in CRMconnect: orders, stock, WMS, invoicing and e-Factura, and EDIconnect sends and receives the Ambient documents from the same data.

How you get started as an Ambient supplier

Ambient connects its suppliers in phases. The steps below are the ones on your side; order and timing are agreed with Ambient.

1. Find out which phase you are in. Phase one started in November 2026 with about 150 suppliers. If you are not sure whether you are in it, ask your contact at Ambient.
2. Set up the Ambient customer. In CRMconnect the Ambient customer is added with its 11 locations and their GLNs, plus the mapping between your item codes and the ones in Ambient orders.
3. Decide where each document comes from. You decide where the order is created (CRMconnect, ERP or both), what the DESADV is generated from (WMS picking or the delivery document) and who issues the invoice.
4. Check the first documents. The first orders and advices are followed document by document until the data goes through without corrections.
5. Work on exceptions only. After start-up, the operator sees only what does not match: unknown items, partial deliveries, receipt differences, held invoices.

Where differences usually appear and how you handle them

Wrong delivery location on the advice or the invoice

The GLN is taken from the ORDERS and carried unchanged into the DESADV and INVOIC. It is not picked by hand from the store name, which can share a GLN with other locations.

Partial delivery because an item is out of stock

The DESADV is built from what was scanned during picking, not from the ordered quantity. The rest stays open on the order or is cancelled, as agreed with Ambient.

The receiving advice shows less than you delivered

The difference appears as a task, per line, with the ordered, delivered and received quantities. You decide whether to accept it or dispute it with your delivery documents.

The invoice does not match the dispatch advice

The invoice uses the same delivery data as the DESADV, and a quantity or price difference holds it until someone checks it.

Returns tracked by email

From December 2026 the return order arrives by EDI and is linked to the Ambient customer, and the correction goes out as a correction / storno invoice.

Questions about EDI with Ambient

Which EDI documents are active with Ambient today?

Four: the order (ORDERS), the dispatch advice (DESADV), the receiving advice (RECADV) and the invoice (INVOIC). The order and the receiving advice come from Ambient; the dispatch advice and the invoice are sent by you.

What changes in EDI with Ambient from December 2026?

Two documents are added: the return order and the correction / storno invoice. Returns and post-invoice corrections then flow by EDI, referencing the original documents.

Which GLN do I use for the Ambient online store?

Ambient PRO Concept On Line (code APWB) has GLN 2008892534120, the same as the head office, the Sibiu store and the Sibiu logistics centre. That is why, in the DESADV and INVOIC, you use the delivery location GLN from the Ambient order, not one chosen by location name.

Can I do EDI with Ambient without an ERP?

Yes. Orders, stock, the warehouse (WMS) and invoicing with e-Factura can run in CRMconnect, and EDIconnect sends and receives the Ambient documents from the same data. If you have an ERP, CRMconnect works alongside it and accounting stays in the ERP.

How are differences between DESADV and RECADV reconciled?

CRMconnect compares the receiving advice with the dispatch advice of the same delivery, line by line. Matching lines are closed, and each difference becomes a task with the ordered, delivered and received quantities, so you can decide to accept or dispute it. From December 2026, a difference accepted after invoicing can be settled with a correction / storno invoice by EDI.

I already have an ERP. Where do Ambient orders go?

Into CRMconnect, where the delivery and the dispatch advice are prepared, and, through the ERP connector, into your ERP. The invoice can be issued from the ERP or from CRMconnect; either way it goes to Ambient through EDIconnect after being checked against the order and the delivery.

Related pages

• EDI with retailers: the EDIconnect page
• Retail chain EDI connection module
• Order Management System (OMS)
• WMS: the warehouse that generates the advice
• Invoicing and e-Factura
• Guide: EDI orders from retail chains