EDI with Ambient: what happens in the supplier's operations once the order arrives
Short answer
Ambient, the DIY and building materials retailer from Sibiu, connects its suppliers by EDI on the Azuvio platform (the EDIconnect module of CRMconnect); phase one started in November 2026 with about 150 suppliers. The documents in use today are the order (ORDERS), the dispatch advice (DESADV), the receiving advice (RECADV) and the invoice (INVOIC); from December 2026 the return order and the correction / storno invoice are added. In CRMconnect, the Ambient order becomes a sales order, WMS picking produces the DESADV, and the receipt and the invoice are checked against what you delivered, with or without an ERP.
This page is for Ambient suppliers who already receive EDI documents or will soon. It shows what each document does in orders, the warehouse and invoicing, which GLN to use for each location, and what changes from December 2026.
Updated 05.11.2026
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.
ORDERS
Order
Sent by Ambient with the items, quantities, requested date and the GLN of the delivery location. In CRMconnect it becomes a sales order for the Ambient customer, with the delivery location filled in from the GLN.
DESADV
Dispatch advice
Sent by you before the goods reach Ambient. It is generated from the closed WMS picking or from the delivery document, so it carries the quantities actually loaded, not the ones ordered.
RECADV
Receiving advice
Sent by Ambient after receipt, stating what was received on each line. CRMconnect compares it with the DESADV of that delivery and shows you only the lines that differ.
INVOIC
Invoice
Sent by you, from the CRMconnect invoicing module or from your ERP. Before it goes out, the invoice is checked against the order, the dispatch advice and, if it has arrived, the receiving advice.
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
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
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
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
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
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.
| Store code | Name | County | City | Address | Postal code | GLN |
|---|---|---|---|---|---|---|
| APHQ | Ambient PRO Concept HeadQuarter | Sibiu | Sibiu | str. Turda 15 | 550018 | 2008892534120 |
| APSB | Ambient PRO Concept Sibiu | Sibiu | Sibiu | șos. Alba Iulia, nr. 100 | 550018 | 2008892534120 |
| APBN | Ambient PRO Concept Bistrita | Bistrița-Năsăud | Bistrița | Calea Moldovei nr. 15A | 420096 | 2008892534137 |
| APMD | Ambient PRO Concept Medias | Sibiu | Mediaș | șos. Sibiului 55 / str. Iacob Pisso 2 | 551129 | 2008892534144 |
| APSG | Ambient PRO Concept Sighisoara | Mureș | Sighișoara | str. Barătilor 2 | 545400 | 2008892534151 |
| APAB | Ambient PRO Concept Alba Iulia | Alba | Alba Iulia | șos. Al. I. Cuza 26 | 510193 | 2008892534168 |
| APHD | Ambient PRO Concept Deva | Hunedoara | Deva | Calea Zarandului, nr. 150A | 330161 | 2008892534175 |
| APVL | Ambient PRO Concept Valcea | Vâlcea | Râmnicu Vâlcea | str. Parcul Industrial, nr. 2 | 240015 | 2008892534182 |
| APSL | Ambient PRO Concept Logistic | Sibiu | Sibiu | str. Turda 15 | - | 2008892534120 |
| APTG | Ambient PRO Concept Targu Mures | Mureș | Târgu Mureș | str. Depozitelor 45-47 | 540198 | 2008892534199 |
| APWB | Ambient PRO Concept On Line | - | - | - | - | 2008892534120 |
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.
- 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.
- 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.
- 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.
- Check the first documents. The first orders and advices are followed document by document until the data goes through without corrections.
- 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
Supplying Ambient? Let's look at your flow
Tell us whether you work with an ERP and how you prepare deliveries. On test data we show you how an Ambient order lands in your orders, how the dispatch advice comes out of picking and where you see receipt differences.