Corporate invoice details (Tax Office, Tax ID, Company Name) and the Turkish ID Number move from Shopify to Entegra without an external server in two ways: the CompliTR app's Entegra invoice module or a serverless Shopify Flow automation. Both collect the data without touching checkout and write it to the order's shipping_address.company field in the format Entegra expects.
This week, several brands came to us with the same technical bottleneck: how do we transfer a customer's corporate invoicing details (Tax Office, Tax ID, Company Name), or the Turkish ID Number for individual invoices, from Shopify to Entegra without an extra server or middleware? This issue affects every store in Turkey that issues corporate invoices from Shopify; however, the solution is much closer than many teams think. We've solved the problem end-to-end with two separate serverless methods, and we explain both with their technical details in this article.
The Problem: Checkout Lock in Non-Plus Stores
Issuing legally compliant e-invoices in Turkey requires integration systems like Entegra to have the customer's tax identification.
For individual customers, a Turkish ID Number is required; for corporate customers, a Tax ID, Tax Office, and Company Name are needed. The problem stems from Shopify's architecture: in non-Shopify Plus stores, the checkout screen cannot be customized. It's not possible to add fields like "Tax ID" or "TC" to the standard checkout flow. Furthermore, Entegra usually reads this information from the order's company field. Therefore, two problems must be solved simultaneously: collecting this data without touching the checkout, and writing the collected data into the order's company field in the format Entegra expects.
The data and format Entegra expects differ for each invoice type:
Critical Note: Once an order is created in Shopify, the billing_address cannot be changed via API. Only the shipping_address can be updated. Therefore, in both solutions below, the writing operation is performed on the shipping_address.company field; Entegra should adjust its reading priority accordingly.
There are two different ways to overcome this limitation.
Solution 1: CompliTR App (Plug-and-Play Module)
CompliTR is our Shopify app that addresses Turkey-specific compliance requirements (KVKK consent, distance sales agreement, ETBIS). We've added a Corporate/Individual Invoice module for Entegra to it. It's activated with a single toggle; there's no need to write code, set up Flow, or rent a server.
How It Works:
1. Data collection in the cart (without touching checkout)
When the module is active, a collapsible "I want a corporate invoice" field automatically appears on the cart page and in the cart drawer, right below the KVKK consent checkbox. When the customer checks it, the following fields open up: Company Name, Tax Office, Tax ID.
This data is instantly saved to the order's cart attributes. The theme code is never manually modified; it's injected to work safely with any theme.
2. Individual (Personal) scenario
For individual invoices, the customer enters their Turkish ID Number into the address details field; the module captures this data.
3. Automatic writing after order creation
As soon as an order is created (via the orders/create webhook), the module activates, formats the collected data, and writes it to the order's shipping_address.company field:
Firma;Acme A.Ş.;1234567890;Beşiktaş / Şahıs;Ayşe Yılmaz;12345678901. This allows Entegra to directly read the tax identification from the company field when fetching orders.
Security Note: This functionality only operates when the module is active. When the module is disabled, no fields are visible in the cart, no data is collected, and the order is not affected.
Benefits of the CompliTR Solution
- Zero technical setup: On-off toggle, live in minutes.
- Theme agnostic: Cart/drawer injection works with any theme, and the theme code remains intact.
- Integrated with KVKK: Consent checkbox, contract, and billing flow in a single app.
- No maintenance overhead: Nodus Works manages Shopify API changes on the application side.
You can review all features of the CompliTR app.
Solution 2: Serverless Automation with Shopify Flow
The second approach is a serverless automation built entirely on Shopify Flow. Entegra is just the use case here; the underlying structure is an automation architecture that removes any dependency on an external server.
The Core of the Architecture
Instead of renting an external server or middleware, we solved all the logic within Flow:
- We built a flow that takes the data the customer enters in the address details (Şahıs;AdıSoyadı;TC; or Firma;FirmaAdı;VergiNo;VergiDairesi),
- captures it by scanning the address hierarchy within Flow (billing_address, then shipping_address),
- and writes the result to the shipping_address.company field
The app token is stored in Flow Secrets; API requests and code execution are handled directly in Flow.
Critical Note: Never embed the token as plain text (string) directly into the flow. Flow Secrets stores the token encrypted and automatically resolves it when referenced within the flow. This is the only secure method recommended by Shopify.
We Set Up the 20+ Step Flow Using a Hybrid Method
Shopify Flow can build multi-step logic; however, manually setting up dozens of steps one by one through the interface is a significant waste of time. To accelerate the process, we integrated AI into the workflow:
1. Prompt preparation: We converted each step we wanted Flow to perform into a clear prompt. We defined the access token within Flow Secret and referenced it in the prompt.
2. Sidekick support: We gave the prompt to Shopify Sidekick to generate the first draft and downloaded it as a .flow file.
3. AI fine-tuning: The .flow file can be edited by hand but is fragile, so we had Claude analyze and fix it at the code level.
4. Import: We re-uploaded the edited file to the system. This allowed us to quickly deploy the 20+ step flow without errors.
This hybrid approach (Sidekick draft + AI editing + import) makes Flow setup noticeably faster than building it manually.
Advantages of the Flow Solution
- Fully serverless: No external servers, webhook infrastructure, or middleware.
- Conditional branching: Adaptable to any scenario, such as "If this field is filled, write this here; otherwise, do that."
- Security within Shopify: The token stays in Flow Secrets; data never leaves the Shopify ecosystem.
- One-time setup: Once properly configured, it requires no maintenance.
If you want to adapt this Shopify Flow-based serverless automation architecture to your own operations, our Shopify integration solutions service also covers Flow setup and testing.
Which Solution Should You Choose?
What separates the two solutions is the kind of need they meet: CompliTR actively collects data from the customer in the cart, while Flow processes and routes data that the customer has already entered into the address fields.
Brief recommendation: If you need an interface to collect data from customers in the cart and want a maintenance-free, fast solution, choose CompliTR. If the data is already being entered into the address fields and you want to connect the process to your own automation network, choose Shopify Flow.
They also work together: You can collect data in the cart with CompliTR and then chain the subsequent operational steps with Flow.
The Bigger Picture: The Evolving World of Shopify Flow
Beyond solving a specific problem for Entegra, the more lasting takeaway is this: For even the smallest data transfer, conditional writing, or API triggering operation, renting a remote server or setting up a custom webhook infrastructure is no longer the first choice.
Shopify Flow eliminates this cost by keeping security and operational control directly within Shopify. With app tokens stored in Flow Secrets and complex 20+ step flows built without leaving the Shopify ecosystem, the operational burden drops to almost zero.
This is not a trend, but an architectural shift. At Nodus Works, we have seen stores that actively use Flow cut both setup and maintenance costs significantly compared with stores that set up external servers for the same scenarios. To put it in numbers: the average monthly server cost of $40-80 for a single integration drops to zero with the Flow architecture.
If you are experiencing similar bottlenecks in your e-commerce operations, evaluate Shopify's native capabilities before investing in external servers.
FAQ: Invoice Transfer from Shopify to Entegra
Can I change the billing address (billing_address) in Shopify after the fact? No. Once an order is created, the billing_address cannot be changed via API; this is a fixed limitation in Shopify's architecture. Only the shipping_address can be updated. Therefore, the tax ID is written to the shipping_address.company field, and Entegra's reading priority is set accordingly.
Can I add fields to the checkout in a non-Plus store? No. Shopify has made adding UI extensions to the information, shipping, and payment steps of checkout available only to Plus plans. In standard stores, new fields can't be added to these steps. Collecting data in the cart and writing it to the address after the order is the only practical method available; CompliTR automatically sets up this flow.
How do you collect the individual customer's Turkish ID number? The customer enters their Turkish ID number into the address details field. The module captures this data, converts it to the format Şahıs;AdıSoyadı;TC, and writes it to the company field. Entegra reads this format and initiates the individual e-invoice process.
Is an external server really not needed? Yes. CompliTR runs on its own app infrastructure; you don't need to rent any server. Flow, on the other hand, runs entirely within Shopify. In both scenarios, the external infrastructure cost is zero.
How are corporate invoices sent from Shopify to Entegra? To transfer corporate invoice data from a Shopify store to Entegra, the customer's Tax ID, Tax Office, and Company Name information is written to the order company field in the format Firma;FirmaAdı;VergiNo;VergiDairesi. In non-Shopify Plus stores, since the checkout cannot be customized, the data is collected in the cart and automatically transferred to the shipping_address.company field when the order is created.
How is the Turkish ID number collected in Shopify? In non-Shopify Plus stores, the Turkish ID number cannot be collected by adding extra fields to the checkout. A practical method is for the customer to enter their Turkish ID number into the address details field, and for this data to be written to the shipping_address.company field in the format Şahıs;AdıSoyadı;TC via an automation (CompliTR or Shopify Flow).
Why can't the Shopify billing_address be changed? Shopify locks the billing_address field as immutable after an order is created. This also applies via the API; a PUT /orders/{id} call rejects billing_address updates. Only the shipping_address can be updated. This architectural constraint necessitates working through shipping_address.company in e-invoice integrations in Turkey.
Conclusion
With the right architecture, you can transfer corporate invoice data and Turkish ID numbers from Shopify to Entegra without an external server. CompliTR stands out as a quick, ready-made solution; Shopify Flow stands out for conditional branching and integration into your own automation network. Both solve the same problem for different user profiles, and when used together, data collection and operational automation steps complement each other.
If you have a similar integration bottleneck, our Shopify integration solutions service can support you with both ready-made apps and Flow-based serverless solutions.
.png)
