Shopify Uyumsoft Integration
Uyumsoft is not a single product: GİB-approved special integrator services and Uyum ERP sit under the same brand. On the Shopify side, an Uyumsoft connection usually means turning an order into an e-invoice or e-archive invoice; syncing stock and price only becomes possible once the ERP side is active. Setup starts with identifying which product is actually in use, the bridge is built from a dedicated integration tool rather than an app published by Uyumsoft itself, and online sales invoices run on their own series.
growing with Nodus Works on Shopify
Shopify Uyumsoft integration what is it?
Shopify Uyumsoft integration is the connection that turns a store order into a record on the Uyumsoft side and issues the legal document from there. If you only hold an e-Transformation agreement, the flow is order, ledger account, invoice. If Uyum ERP is also active, stock and price get written back to the store from Uyumsoft.
Setup starts by identifying which Uyumsoft product is actually in use. On the integrator side, the GİB registration and the document credit package are confirmed; on the ERP side, access and licensing are cleared separately. Uyumsoft has no app of its own in the Shopify App Store, so the bridge is built through whichever integration tool you use.
Once the connection is live, the daily flow runs from one place: the order lands in Uyumsoft, a ledger account is opened or matched, and the document is issued with Uyumsoft's own stamp. If your marketplace invoices already run through the same stamp, Shopify just adds another channel to that same table; making sure the same order doesn't produce two documents is solved during setup.
What gets synced between Shopify and Uyumsoft
Which items sync depends on which product you hold. The six items below cover the most common questions in a Shopify Uyumsoft integration; stock and price only come into play once the ERP side is active.
Shopify orders transferred to Uyumsoft
When an order is placed in the store, it's written to Uyumsoft. In a setup that only uses the integrator, this record is the source of the document; with ERP active, a sales order record is also created and the invoice is generated from it.
Ledger account creation and matching
The buyer's details turn into a ledger account: if one already exists it's matched, otherwise a new one is opened. If the matching field is set up wrong, a second account gets created for the same person and has to be merged by hand.
e-invoice and e-archive invoice stamp
The document goes to GİB through Uyumsoft's special integrator infrastructure. If the buyer is an e-invoice taxpayer they get an e-invoice, otherwise an e-archive invoice is issued. Shopify's own order confirmation does not replace this document.
Stock and price written back to the store
This item only runs once Uyum ERP is active. From that point, the real catalog lives in Uyumsoft; which warehouse and which price list feed the store is the critical decision in setup. An e-Transformation-only agreement doesn't include this flow at all.
Online sales invoice series
Documents for sales made online cannot share a series with in-store or wholesale sales. The series is opened at the very start of Uyumsoft's document structure; a past document's series cannot be changed afterward.
Cancellation and return documents
The cancellation window is short; after it closes, a return invoice is the only option. Assuming a return equals a cancellation doesn't hold up by month end — the two documents have to be offset against each other. Since sources disagree on the exact number of days, it isn't stated here; confirm it with your Uyumsoft account manager.
Which Uyumsoft product does the integration connect to?
Two separate products sit under the same brand. If this distinction isn't made clear on day one of setup, every step after it builds on the wrong expectation.
e-Transformation: stamps and archiving
GİB-approved special integrator services sit here. e-invoice, e-archive invoice, e-waybill and e-ledger are all issued from Uyumsoft's infrastructure. For many Shopify stores this is the only real need: turning an order into a legal document.
Uyum ERP: stock, ledger, orders
The ERP side carries production, stock, finance and the ledger. Writing stock and price to the store, choosing warehouse splits and price lists — all of that decision-making happens here. Without ERP, none of these items connect.
Hosting depends on the product
e-Transformation is a cloud service; no on-premise server sits in the middle. Uyum ERP can run either in the cloud or on your own server; a server-based setup needs a secure access path opened separately.
Credits are tied to documents
Sending an official document consumes credits. This isn't a model where every stock lookup costs something; once a package runs out, no new document is issued. Packages are sized against your monthly order volume.
Uyumsoft doesn't publish the bridge itself
Uyumsoft has no app of its own in the Shopify App Store. The connection is built through an integration tool or a project-specific middle layer; the boundary of responsibility is set out in the agreement.
If a marketplace stamp is already there
If your Trendyol or Hepsiburada invoices already come out of Uyumsoft, Shopify just becomes another channel feeding the same stamp. Preventing the same order from producing two documents, or the same customer from getting two ledger accounts, is solved at this stage.
In practice, the first question in a setup meeting is the license list. If you only hold a special integrator agreement, this page is your invoice bridge. If ERP is also in place, stock and price are designed separately. Treating the two as one story ends up getting the project built twice.
How is Shopify Uyumsoft integration set up?
The six steps below cover setup from identifying the product to the first test document. Skip the first step and the other five get built against the wrong product.
Identify which Uyumsoft product is active
Is it an e-Transformation agreement, Uyum ERP, or both? Clarify this with your Uyumsoft partner at uyumsoft.com. This list determines which document and which record gets transferred.
Confirm the GİB registration and credit package
On the special integrator side, confirm that your tax registration runs through Uyumsoft and that the credit package covers your monthly document volume. Once a package runs out, no new document is issued — this happens quietly in most setups.
If you use ERP, prepare access
Cloud ERP doesn't need a server in the middle. In a server-based setup, a secure access path is opened, and which company and which period the bridge writes to is decided. Once a period is closed, no records land in it.
Define ledger, product and series matching
Write down which field matches the customer to a ledger account, whether products match by barcode or SKU, and which invoice series is used for online sales. If you sell to businesses, this step also settles where the tax ID and company name are collected during checkout.
Set up the shipping line, currency and return rule
Whether shipping cost is added to the invoice as a line item, and at what rate, is defined in setup — the rate isn't guessed, it's confirmed with a test document. If you sell in foreign currency, which day's exchange rate applies is written down. A return issued after the cancellation window closes is set up as a separate flow.
Verify the document and stock with a single order
Place a single-item order and confirm the record lands in Uyumsoft, the ledger account opens correctly, and the document comes out with the right series and the right stamp. If ERP is active, also check that stock drops in the store in the same test. If you have marketplace channels, check that the same order doesn't produce a second document.
The table below shows what each Shopify record maps to on the Uyumsoft side. The stock and price rows only fill in once ERP is active.
| What's in Shopify | Its counterpart in Uyumsoft |
|---|---|
| Order | Document source; a sales order record too, if ERP is active |
| Customer | Ledger account; the matching field is chosen during setup |
| Product | Stock card, once ERP is active |
| Variant | Expected as a separate stock card; the vendor's rule here isn't clearly documented |
| Price | The selected price list, ERP only |
| Stock | Quantity in the selected warehouse, ERP only |
| Invoice | e-invoice or e-archive invoice, with Uyumsoft's stamp |
| Return | Return document or cancellation, depending on timing |
| No counterpart | Tax ID and company name; credit balance; company and period |
The table's last row lists three items Shopify doesn't hold natively. If the tax ID isn't collected at checkout, every order is treated as a final consumer sale. Credit balance is only tracked on the Uyumsoft side. Company and period settings determine which taxpayer a record is written under in an ERP setup.
Tell us about your catalog and your current setup, and let's work out together how Shopify Uyumsoft integration fits your product structure. No form to fill in — reach us directly by phone, email or WhatsApp.
Invoicing only, or stock too?
In most stores, an Uyumsoft search boils down to one expectation: when an order comes in, a legal document should follow. An e-Transformation agreement covers exactly that. Stock, price and warehouse splits are a separate product, and set up separately.
In a store where only the document bridge is set up, the catalog keeps living in Shopify. Uyumsoft doesn't hold stock, manage a price list, or carry the variant matrix in that setup. All that's expected is that the order turns into a ledger account and a document.
Once Uyum ERP is active, the direction reverses: the real catalog lives in Uyumsoft, and the store just publishes it. Which warehouse goes online and which price list feeds the site is decided at this point. Connect the wrong store list and the wrong price goes live.
When both products are in play, order matters. The document series, ledger matching and GİB stamp go live first; writing stock to the store is the second wave. Turning both on the same day is how the wrong warehouse or the wrong list ends up live.
How is the online sales invoice issued in Uyumsoft?
The document comes out of Uyumsoft, not Shopify. The six points below come straight from regulation; the system's name changes, the rule doesn't.
Online sales need their own series
Shopify orders can't share a series with in-store or wholesale sales. The series is opened at the very start of Uyumsoft's document structure. A past document's series cannot be changed afterward.
The invoice has mandatory fields
The invoice must include the website the sale was made on, the payment method, the payment intermediary, the payment date, the tax or ID number of whoever carried the goods, the shipping date, a returns section, and a statement that the sale was made online. If the transfer can't read these from the order, the field is left blank.
A paper copy travels with the goods
A printed copy of the invoice travels with the shipped goods; the store's packing slip doesn't replace it. The rule changes the packing station, not the accounting: the label and the invoice printout get pulled at the same step.
The cancellation window is short; after it, a return document
Once the window passes, a correction is made with a new document, not a cancellation, and the two documents are offset against each other. The exact number of days isn't stated here since sources disagree. Assuming a return equals a cancellation doesn't hold up by month end.
No record lands in a closed period
If an order sits in the queue near month end and the period closes, the record gets rejected — this happens quietly in most setups. Having the bridge raise an alert when it fails is part of the setup.
Shopify's confirmation isn't the invoice
The legal document always comes out of Uyumsoft. The integration's job isn't to send the customer some output — it's to issue the document from the right series, at the right rate.
Business invoice details (tax ID, tax office, company name) aren't collected by default at Shopify checkout. Without these fields, Uyumsoft treats every order as a final consumer sale. If you sell to businesses, where this information gets collected is worked out during setup.
How are the ledger, product and variant matched?
Because the bridge opens a ledger account from every order, a wrong matching field lets that table balloon. In Uyumsoft, merging duplicates afterward is a manual job.
Duplicate ledger accounts
The same person creates a second account when they show up with a different email, phone number, or as a guest order. A separate rule is set for guest orders; otherwise the ledger list becomes unreadable by month end.
Products don't match by name
Titles change, barcodes don't. With ERP active, matching runs on barcode or SKU. Mixing up a case barcode with a single-unit sales barcode breaks stock quietly.
Variant mapping isn't clearly published
Uyumsoft's own documentation doesn't officially describe a built-in variant model like Shopify's. The practical expectation is a separate stock card per color and size; that's not a documented rule, it's something you confirm with a test record.
The exchange rate decision is written down
Shopify can sell in multiple currencies, but the accounting record is entered converted to local currency. If which day's rate applies isn't defined, reconciliation drifts by small amounts every month.
Tax on the shipping line
Whether shipping cost is added to the invoice as a line item, and at what rate, is defined during setup. The rate isn't guessed — it's confirmed with a test document.
Marketing copy doesn't live in ERP
Search copy, collection structure and storefront descriptions aren't stored in Uyumsoft. If the transfer overwrites these fields, weeks of writing disappear in a single sync; the fields to protect are flagged in advance.
If marketplace invoices already come out of Uyumsoft
In many brands, Uyumsoft was originally chosen for marketplace invoicing. Once Shopify is added later, the same stamp has to handle two sources at once.
A second channel into the same stamp
If Trendyol and Hepsiburada orders are already documented through Uyumsoft, Shopify gets written into the same infrastructure. The upside is a single archive and a single credit pool. The risk is the same order getting documented twice by two separate transfers.
Duplicate ledger accounts
A marketplace customer is usually opened under the marketplace order number, a Shopify customer under their email. When the same person shops on both channels, two ledger accounts get created. Without a matching rule shared across channels, reports balloon.
Stock gets reserved twice
With ERP active, the marketplace transfer and the Shopify transfer can each deduct from the same warehouse separately. Review the existing reservation rule before adding a new channel.
One shared credit pool
Document credits aren't split by channel. On a heavy campaign day, marketplace and Shopify orders drain the same package together; once it's gone, no new document is issued. Monitoring only looks at one balance.
Returns get documented per channel
A marketplace return follows the marketplace's own rule, a Shopify return follows the store's rule. Both produce a document in Uyumsoft, but the source order number is different. Offsetting is therefore set up with a channel tag.
Watching it from one screen
Two sources writing into the same stamp means you need to see the order and the document side by side. That's what Station is for: which channel produced which document sits on one screen.
Three common problems and how we fixed them
The three setups below show how we've handled Shopify Uyumsoft integration issues in stores we've connected.
Assuming stock would sync too while waiting for documents
Problem The store was connected to Uyumsoft and orders were turning into documents, but stock on the site was still updated by hand. The team thought the integration was half-finished.
Cause They only held an e-Transformation agreement. With Uyum ERP not active, stock and price were never meant to be written from Uyumsoft to the store — the bridge was producing documents exactly as designed, nothing more.
Fix We clarified the scope: the document bridge and the stock bridge are separate. Since stock sync was actually wanted, the ERP license and warehouse decision were planned as a second, separate project. The existing document flow was left untouched.
Every business order showing up as a final consumer sale
Problem By month end, Uyumsoft's ledger accounts were full of personal names; invoiced companies had no tax ID on the document. Accounting was correcting every record by hand.
Cause Shopify checkout wasn't collecting the tax ID, tax office, or company name. The transfer wrote the blank field to Uyumsoft as a final consumer sale.
Fix Business-info fields were added to checkout, and the matching rule for existing ledger accounts was switched from email to tax ID. New business orders started producing documents under the correct company name.
The marketplace and Shopify documenting the same order twice
Problem On a campaign day, some orders ended up with two documents in Uyumsoft. Credits ran out faster than expected, and the customer received two document numbers.
Cause The marketplace transfer and the Shopify transfer were both writing to the same stamp without sharing the order number — the same basket was being read as two separate sources.
Fix Source-tagged deduplication was set up: the marketplace order number or the Shopify order number became the document key. The second write was rejected, and credit consumption returned to normal.
Station is the tool we built to watch orders, stock, price and invoicing from a single panel. If your marketplace channels also write into the same Uyumsoft stamp, this is where you catch the duplicate-document risk.
Frequently Asked Questions
How is Shopify Uyumsoft integration set up?
Does Uyumsoft have an official Shopify app?
Are Uyumsoft e-invoice and Uyum ERP the same thing?
Is connecting only e-invoice enough?
Are Uyumsoft e-invoice and e-archive invoice issued automatically on Shopify orders?
Does the online sales invoice need its own series?
What information must appear on the online sales invoice?
How is business invoice information collected?
What are credits, and how do they affect the integration?
Does stock get written from Uyumsoft to Shopify?
Which warehouse's stock gets exposed to the store?
Which field do products match on?
How are variants represented in Uyumsoft?
Are a cancellation and a return the same document?
Can an order be written into a closed period?
My marketplace invoices already come out of Uyumsoft — is Shopify set up separately?
What changes if Uyumsoft runs on our own server?
How long does the integration take?
How does a foreign-currency sale show up on the invoice?
Is the shipping fee added to the invoice?
BİZİ TERCİH
EDENLERİN ARASINDA
YER ALIN...
Herkes için Shopify çözümleri üretiyoruz.
Yeni bir Shopify mağazası kurmak, mevcut mağazanızı geliştirmek, özel entegrasyonlar yapmak veya hız problemlerini çözmek mi istiyorsunuz? Biz, teknik işleri sizin yerinize çözen uzman bir Shopify partneriyiz.

Dossha
#shopify

Les Benjamins
#shopify

Nocturne
#shopify

Fellas
#shopify

Mai
#shopify

Karaca
#shopify

Milagron
#shopify

Kiğılı
#shopifySeo

Şölen
#shopify

Adell
#shopifyB2B

Ohora
#shopify

Rendrea
#shopifyBooking

Babeskin
#shopify

The New Lab
#shopify

DTF Town
#shopify

Eczaclick
#shopifySeo

Termos Dünyası
#shopify

Halı.net
#shopify

Blend-r
#shopify

Oioi
#shopifySeo

Nowshopfun
#shopify

Marie Claire
#shopify

Gaziburma
#shopify

Dünyada Kitap
#shopify
NEDEN BİZİMLE
ÇALIŞMANIZ GEREKTİĞİNİ
SİZE ANLATMAK İSTERİZ
Shopify'ı çok iyi anlıyoruz; Türkiye'de her segmentin karşısına biz olarak çıkıyoruz :)







Sadece Shopify konuşanlardan oluşan bir takım

Hey!
Bannerlarım kesik gözüküyor :(
Yardım eder misiniz, kampanya dönemindeyim.
Selam Elif!
2 dakikaya çözüyoruz.





.webp)
.webp)


