This week, we heard the same technical bottleneck from several brands: How do we transfer a customer's corporate invoicing information (Tax Office, Tax ID, Company Name) or individual invoicing's Turkish ID Number from Shopify to Entegra without an additional server or middleware? At Nodus Works, we've observed that this issue affects a large portion of brands using Shopify in Turkey; 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, ETBİS). 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;12345678901This 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 application.
- No maintenance overhead: Nodus Works manages Shopify API changes on the application side.
All features of the CompliTR application apps.nodusworks.com/uygulamalar/complitr you can review.
Solution 2: Serverless Automation with Shopify Flow
The second approach is a serverless automation built entirely on Shopify Flow. Entegra serves only as the trigger scenario here; the core architecture lays out an automation architecture that completely eliminates external server dependency.
The Core of the Architecture
Instead of renting an external server or middleware, we solved all the logic within Flow:
- The data entered by the customer into the address details (Individual;NameSurname;ID; or Company;CompanyName;TaxNo;TaxOffice),
- that captures by scanning the address hierarchy within Flow (billing_address and then shipping_address),
- and writes the result to the shipping_address.company field
We set up a flow. The app token is stored in Flow Secrets; API requests and code execution are managed directly from 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: By providing the prompt to Shopify Sidekick, we generated the initial draft and downloaded it as a .flow file.
3. AI fine-tuning: We had Claude analyze and correct the .flow file at the code level, as it is open to manual intervention and sensitive.
4. Import: We re-uploaded the edited file to the system. This allowed us to quickly deploy the 20+ step flow without errors.
At Nodus Works, we observed that this hybrid approach (Sidekick draft + AI editing + import) reduces the Flow setup time by approximately 3 times compared to manual setup alone.
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: In Token Flow Secrets, data does not leave the Shopify ecosystem.
- One-time setup: Once properly configured, it requires no maintenance.
If you want to adapt the Shopify Flow-based serverless automation architecture to your own operations Our Shopify integration solutions service also covers the Flow setup and testing process.
Which Solution Should You Choose?
The key differentiator between the two solutions is the needs profile: 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 primary option.
Shopify Flow eliminates this cost by keeping security and operational control directly within Shopify. By storing app tokens in Flow Secrets and building complex 20+ step flows without leaving the Shopify ecosystem, the operational burden is reduced to almost zero.
This is not a trend, but an architectural shift. At Nodus Works, we have observed that stores actively using Flow, compared to those setting up external servers for the same scenarios, significantly reduce both setup and maintenance costs. 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 only made Checkout Extensibility available to Plus plans. In standard stores, the checkout UI cannot be customized. 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 Individual;NameSurname;TurkishID, 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 application 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 Company;CompanyName;TaxID;TaxOffice. 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 Individual;NameSurname;TurkishID 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
Corporate invoice and Turkish ID number transfer from Shopify to Entegra is solved without an external server with the right architecture. CompliTR stands out for a quick and ready-made solution; Shopify Flow 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, from our Shopify integration solutions service, you can get support for both ready-made applications and Flow-based serverless solutions.
