What to tell your ERP integrator
“The fields are in the order’s Additional details, as customAttributes or note_attributes in webhooks. The order receives the Τιμολόγιο tag. Map the exact fields below to the ERP customer card and order, matching an existing or new customer by Α.Φ.Μ (VAT number). Nothing else in the existing sync changes: products, prices, taxes, order completion and transformation to an invoice continue as today.”
Where your provider reads the data
Invoice fields are saved as Shopify order customAttributes. In order webhook payloads, the corresponding list is note_attributes, using name/value pairs. Shopify Admin displays these as Additional details. The Greek keys stay the same across interface languages.
| Exact key | Meaning |
|---|---|
| Έκδοση Τιμολογίου | Invoice request: ΝΑΙ; receipt choice: ΟΧΙ |
| Α.Φ.Μ | VAT identifier |
| Επωνυμία | Company name |
| Δ.Ο.Υ | Greek tax office, where applicable |
| Επάγγελμα | Business activity, where returned |
| Διακριτικός Τίτλος | Trading name, where returned |
| Οδός | Street |
| Αριθμός οδού | Street number |
| Πόλη | City |
| Τ.Κ | Postal code |
| Χώρα | Country derived from the VAT identifier |
Tags and customer reuse
The Τιμολόγιο tag identifies invoice requests. ΑΦΜ προς έλεγχο indicates pending verification and ΑΦΜ μη έγκυρο an invalid result. Tags are workflow signals, not substitutes for the business fields. Customer reuse uses the afm_filler.invoice_details customer metafield; do not confuse that customer record with order attributes.
Send your provider this request
“Read the order custom attributes using the exact keys above. Map ΝΑΙ and ΟΧΙ to our document-request workflow. Hold unresolved verification for staff review, and explain how changes after the initial import update your record.”
For example, test an invoice request whose VIES response is initially unavailable. When the order later receives verified fields, check whether the provider imports that change or needs staff action. Also test a receipt choice and a manually created draft that becomes an order.
No named provider connector is asserted here. Compatibility requires a checked field mapping. Your existing provider issues the actual tax document and handles myDATA; MyTimologio collects and saves the details. Follow installation to create the test records.
Related questions
What must our ERP integrator map?
Read Additional details: customAttributes in Shopify, or note_attributes in order webhooks. Map the exact keys «Έκδοση Τιμολογίου» (ΝΑΙ / ΟΧΙ), «Α.Φ.Μ», «Επωνυμία», «Δ.Ο.Υ», «Επάγγελμα», «Διακριτικός Τίτλος», «Οδός», «Αριθμός οδού», «Πόλη», «Τ.Κ» and «Χώρα» to the ERP customer card and order. Recognise invoice requests by the «Τιμολόγιο» tag and match an existing or new customer by VAT number. Everything else in the sync continues as before.
What happens when AADE or VIES is unavailable?
An unavailable service is treated differently from an invalid number. Orders awaiting verification can carry the tag «ΑΦΜ προς έλεγχο». The code retries pending orders within a three-day lookback window; unresolved tags remain for staff afterwards. Check the order before issuing a document and make sure your provider can handle later field updates.
Can staff reuse a customer’s saved details?
Yes. The app can save invoice details to the customer metafield afm_filler.invoice_details and reuse them in admin workflows such as a later draft order. A returning customer’s details should still be reviewed when the business information changes. Do not assume every anonymous or accelerated purchase automatically reuses them.