Shopify Uyumsoft Integration

Uyumsoft is not a single product: GİB-approved special integration and Uyum ERP sit under the same roof. On the Shopify side a Uyumsoft connection usually means producing an e-fatura or e-arşiv from the order; writing stock and price as well is only possible when the ERP side is open. Setup starts by discovering which product is active, the bridge is built from an integration tool rather than an app the vendor publishes itself, and an internet-sale invoice has a series of its own.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Uyumsoft integration what is it?

A Shopify Uyumsoft integration is the connection that turns a store order into a record on the Uyumsoft side and produces the legal document from there. If you only hold an e-Dönüşüm contract, the flow is order, account and invoice. If Uyum ERP is also open, stock and price are written to the store from Uyumsoft.

Setup starts by discovering which Uyumsoft product is in use. On the integrator side the GİB registration and the credit pack are confirmed; on the ERP side access and license are made clear as well. Uyumsoft has no app of its own in the Shopify app store, so the bridge is built through the tool you use.

Once the connection is live, daily work runs from one place: the order lands in Uyumsoft, an account card opens or is matched, and the document goes out with the Uyumsoft seal. If your marketplace invoices already leave from the same seal, Shopify adds one more channel to that picture; the same order producing two documents is solved during setup.

WHAT SYNCS

What syncs between Shopify and Uyumsoft

What syncs changes with the product you hold. The six headings below cover the questions that come up most often in a Shopify Uyumsoft integration; stock and price only come in when the ERP side is open.

Transfer of Shopify orders into Uyumsoft

When the order is created in the store it is written into Uyumsoft. In a setup that only uses the integrator, that record is the source of the document; when ERP is open an order slip is also created and the invoice is derived from it.

Opening and matching a customer account

The buyer's details turn into an account card; if a card already exists it is matched to that, otherwise a new card is opened. If the matching field is set wrongly a second card is produced for the same person and merging is done by hand.

e-fatura and e-arşiv seal

The document goes to GİB on Uyumsoft's special-integrator infrastructure. If the buyer is an e-fatura taxpayer an e-fatura is issued, otherwise an e-arşiv. Shopify's order output does not stand in for that document.

Writing stock and price to the store

This item runs when Uyum ERP is open. The catalog's truth then sits in Uyumsoft; which warehouse and which price list are attached to the store is the critical setup decision. That flow does not exist on an e-Dönüşüm contract alone.

Internet-sale invoice series

Documents for sales made over the internet cannot be written to the same series as store or wholesale sales. The series is opened at the start of Uyumsoft's document layout; the series of a past document does not change later.

Cancellation and return document

The cancellation window is short, after that a return invoice. A transfer built on the assumption that a return equals a cancellation does not reconcile at month end; the two documents are offset. Sources disagree on the number of days, so a day count is not given; you confirm it with your Uyumsoft consultant.

TWO PRODUCTS

Which Uyumsoft product is the integration built on?

Two jobs sit under the same brand. If the first day of setup does not make this split clear, every later step produces the wrong expectation.

e-Dönüşüm: seal and archive

GİB-approved special integration sits on this side. e-fatura, e-arşiv, e-irsaliye and e-defter go out on Uyumsoft infrastructure. For many Shopify stores this is the only need: producing a legal document from the order.

Uyum ERP: stock, accounts, orders

The ERP side carries production, stock, finance and accounts. Writing stock and price to the store, the warehouse split and the price-list decision are born here. Without ERP those items are not connected.

Where setup lives changes with the product

e-Dönüşüm is a cloud service, no server sits in between. Uyum ERP can run in the cloud or on your own server; on a server install a secure access path is opened as well.

Credits are tied to the document

Sending an official document drops credits. This is not a model where every stock query is billed; when the pack runs out, no new document is issued. The pack is planned against monthly order volume.

Uyumsoft does not publish the bridge

Uyumsoft has no app of its own in the Shopify app store. The connection is built from an integration tool or a project-specific middle layer; the ownership line is written in the contract.

If the marketplace seal is already there

If your Trendyol or Hepsiburada invoices already leave from Uyumsoft, Shopify becomes an extra channel on the same seal. The same order producing two documents, and the same customer opening two accounts, are solved in that picture.

The practical result is this: the first question in the setup meeting is the license list. If you only hold a special-integrator contract, the work is an invoice bridge. If ERP is also in place, stock and price are designed as a second job. Treating the two as one story makes you set the project up twice.

SETUP

How is the Shopify Uyumsoft integration done?

The six steps below cover the setup, from product discovery through the first test document. If the first step is skipped, the next five are built on the wrong product.

Discover which Uyumsoft product is open

Is there an e-Dönüşüm contract, Uyum ERP, or both? Make this clear with the partner you work with through uyumsoft.com. That list decides which document and which record will be transferred.

Confirm the GİB registration and the credit pack

On the special-integrator side, check that the taxpayer relationship runs through Uyumsoft and that the credit pack covers your monthly document volume. When the pack runs out, no new document is issued; in most setups this happens silently.

If you use ERP, prepare access

On cloud ERP no server sits in between. On a server install a secure access path is opened, and which firm and which period the bridge will write to is decided. After the period closes, no record is posted to that period.

Define account, product and series matching

Write which field the customer is bound to the account on, whether the product matches on barcode or stock code, and which invoice series will be used for internet sales. If you sell to businesses, where tax ID and legal title are collected at checkout is also solved in this step.

Set the shipping line, currency and return rule

Whether the shipping charge is added to the invoice as a line, and its rate, is defined during setup; the rate is not assumed, it is seen on a test document. If you sell in a foreign currency, which day's rate is used is written down. The return document after the cancellation window is set up separately.

Verify the document and the stock with a single order

Place an order with a single product and see that the record lands in Uyumsoft, that the account opens correctly, and that the document goes out on the right series and with the right seal. If ERP is open, also check in the same test that stock drops in the store. If you have marketplace channels, also look that the same order does not produce a second document.

The table below shows which Shopify records map to which counterparts on the Uyumsoft side. The stock and price rows are filled only when ERP is open.

What Shopify has	What it maps to in Uyumsoft
Order	Document source; an order slip if ERP is open
Customer	Account card, matching field chosen during setup
Product	Stock card, when ERP is open
Variant	A separate stock card is expected, the vendor rule is not clear
Price	The selected price list, ERP only
Stock	Quantity of the selected warehouse, ERP only
Invoice	e-fatura or e-arşiv, Uyumsoft seal
Return	Return document or cancellation, depends on the window
No Shopify counterpart	Tax ID and legal title; credit balance; firm and period

The last row of the table is three items Shopify does not carry natively. If tax ID is not collected at checkout, every order is treated as a final consumer. Credit balance is watched only on the Uyumsoft side. Firm and period data decide which taxpayer the record is written to in an ERP setup.

Where are you in the setup?

Tell us about your catalog and current setup, and we will work out how the Shopify Uyumsoft integration should be built for your product structure. You do not need to fill in a form, reach us directly by phone, email or WhatsApp.

Get in touch 0850 888 2815 hub@nodusworks.com WhatsApp

WHICH PRODUCT

Invoice only, or stock as well?

Most Uyumsoft searches in stores collapse into a single expectation: when the order lands, a legal document should come out. That expectation is met with an e-Dönüşüm contract. Stock, price and the warehouse split are a separate product and are set up separately.

In a store that only has a document bridge, the catalog keeps living in Shopify. In that setup Uyumsoft does not hold stock, does not manage a price list and does not carry a variant matrix. What is expected is the order turning into an account and a document.

When Uyum ERP is open the direction reverses: the catalog's truth sits in Uyumsoft, the store publishes it. Which warehouse will be opened to the internet and which price list will be written to the site are decided at this point. If the store list is attached, the wrong price drops.

If both products are in place, order matters. First the document series, account matching and the GİB seal come up; writing stock to the store is the second wave. Opening both on the same day lets the wrong warehouse or the wrong list go live.

INVOICES

How is an internet-sale invoice issued in Uyumsoft?

The document comes out of Uyumsoft, not Shopify. The six items below come from regulation; the system name changes, the rule does not.

Internet sales require a separate series

Shopify orders cannot be written to the same series as store or wholesale sales. The series is opened at the start of the Uyumsoft document layout. The series of a past document cannot be changed later.

The invoice has required fields

The web address where the sale was made, the payment method, the organization that mediated the payment, the payment date, the tax or identity number of the party that carried the goods, the date the goods were sent, a returns section and a statement that the sale was made over the internet must be present. If the transfer cannot read these from the order, the field stays empty.

The paper copy goes with the goods

The paper copy of the invoice travels with the shipped goods; the store's packing slip does not stand in for it. The rule changes the packing station, not accounting: the label and the invoice output are taken in the same step.

The cancellation window is short, after that a return document

When the window has passed, the correction is made with a new document, not a cancellation, and the two documents are offset. A day count is not given; sources disagree. The assumption that a return equals a cancellation does not reconcile at month end.

No record is opened in a closed period

If an order that lands near month end sits in the queue while the period closes, the record is refused, and in most setups this happens silently. The bridge raising an alert when it errors is part of the setup.

A Shopify document is not an invoice

The legal document always comes out of Uyumsoft. The job of the integration is not to send the customer an output, it is to produce a document on the right series and at the right rate.

Corporate invoice details (tax ID, tax office, legal title) are not collected as standard at Shopify checkout. If those fields are missing, Uyumsoft treats every order as a final consumer. If you sell to businesses, where those details are collected is solved during setup.

MATCHING

How are accounts, products and variants matched?

Because the bridge opens a card from the order, a wrong matching field inflates the table. Merging on the Uyumsoft side is done by hand later.

Duplicate accounts

When the same person arrives with a different email, phone or as a guest, a second card forms. A separate rule is set for guest orders; otherwise the account list becomes unreadable at month end.

Product matching is not built on the title

The title changes, the barcode does not. When ERP is open, matching is built on barcode or stock code. Mixing a pack barcode with a single-sale barcode breaks stock silently.

The variant counterpart is not published clearly

A native variant model like Shopify's is not described officially on the Uyumsoft side. The practical expectation is a separate stock card for every color and size; that is not a rule, it is confirmed with a test record.

The exchange-rate decision is written down

Shopify can sell in more than one currency; the accounting record enters after conversion into local currency. If which day's rate is used is not defined, reconciliation breaks every month with small differences.

Tax on the shipping line

Whether the shipping charge is added to the invoice as a line, and its rate, is defined during setup. The rate is not assumed; it is seen on a test document.

Marketing copy does not live in the ERP

Search text, collection structure and storefront description are not held in Uyumsoft. If the transfer overwrites those fields, weeks of written content disappear in a single sync; the fields to keep are marked.

MULTICHANNEL

If marketplace invoices already come out of Uyumsoft

In many brands Uyumsoft was first chosen for marketplace invoices. When Shopify is added later, the same seal sees two sources at once.

A second channel on the same seal

If Trendyol and Hepsiburada orders are documented from Uyumsoft, Shopify is written to the same infrastructure. The advantage is a single archive and a single credit pool. The risk is the same order producing two documents from two transfers.

Duplicate accounts

A marketplace customer is often opened with the marketplace order number, a Shopify customer with email. When the same person shops on two channels, two accounts form. If the matching rule is not shared across channels, the report inflates.

Stock is reserved twice

If ERP is open, the marketplace transfer and the Shopify transfer can drop the same warehouse separately. The current reservation rule is reviewed before a new channel is added.

The credit pool is shared

Document credits are not split by channel. On a busy campaign day the marketplace and Shopify finish the pack together; no new document is issued. Monitoring looks at a single balance.

A return is documented by its channel

A marketplace return comes back under the marketplace rule, a Shopify return under the store rule. Both produce a document in Uyumsoft, but the source order number is different. That is why the offset is set up with a channel label.

Looking from a single panel

Two sources writing to the same seal wants the order and the document seen side by side. That is why Station comes in: which channel produced which document sits on one screen.

SCENARIO

Three common problems and how they were solved

The three setup scenarios below show how we handled Shopify Uyumsoft integration problems we solved in stores we connected.

Expecting stock to sync while waiting for the document

ProblemThe store was connected to Uyumsoft, orders turned into documents, but stock on the site was still updated by hand. The team thought the integration had been left half done.

CauseThey only held an e-Dönüşüm contract. Because Uyum ERP was not open, stock and price were not written from Uyumsoft to the store; the bridge was only producing documents, as designed.

SolutionThe expectation was made clear: the document bridge is separate, the stock bridge is separate. If stock was wanted, the ERP license and the warehouse decision were planned as a second job. The existing document flow was left untouched.

Every corporate order looking like a final consumer

ProblemAt month end Uyumsoft accounts were filled with person names; the tax ID of the firms being invoiced was missing from the document. Accounting was correcting every record by hand.

CauseShopify checkout was not collecting tax ID, tax office or legal title. The transfer was writing the empty field into Uyumsoft as a final consumer.

SolutionCorporate-detail fields were added to the payment flow, and the matching rule for existing accounts was pulled from email to tax ID. New corporate orders started producing documents under the right legal title.

The marketplace and Shopify documenting the same order twice

ProblemOn campaign day some orders had two documents in Uyumsoft. Credits ran out faster than expected, and the customer received two numbers.

CauseThe marketplace transfer and the Shopify transfer were writing to the same seal without sharing an order number. The same basket was treated as two sources.

SolutionSource-labelled deduplication was set up: the marketplace order number or the Shopify order number became the document key. The second write was refused, and credit use returned to normal.

STATION

Shopify Uyumsoft integration

Station is the tool we built to watch the order, stock, price and invoice flow from a single panel. If your marketplace channels also write to the same Uyumsoft seal, you see the duplicate-document risk here.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

How is the Shopify Uyumsoft integration done?

Setup starts by discovering which Uyumsoft product is open: e-Dönüşüm, Uyum ERP, or both. Then the GİB registration and the credit pack are confirmed, access is prepared if ERP is in place, account and series matching are built, and the shipping line and return rule are written down. The last step is a test order with a single product producing a document on the right series.

Does Uyumsoft have an official Shopify app?

Uyumsoft has no app that it publishes itself in the Shopify app store. The bridge is built from an integration tool or a project-specific middle layer. No ready-made connector announcement that names Shopify was found on Uyumsoft's site in this review.

Are Uyumsoft e-invoice and Uyum ERP the same thing?

They are not. e-Dönüşüm is GİB-approved special integration, and its job is to seal the legal document. Uyum ERP carries stock, accounts, orders and finance. Many stores only need the first; syncing stock wants the second product.

Is connecting e-invoice alone enough?

Yes, if you want a legal document from the order. If you will also manage stock, price and the warehouse split from Uyumsoft, Uyum ERP has to be open and that side has to be set up separately.

Are Uyumsoft e-fatura and e-arşiv issued automatically on a Shopify order?

They are, once the bridge is built. The document is created inside Uyumsoft, goes to GİB on the special-integrator infrastructure, and the number comes back. If the buyer is an e-fatura taxpayer an e-fatura is issued, otherwise an e-arşiv. Shopify's own output does not stand in for that document.

Is a separate series required for internet-sale invoices?

It is. Documents for sales made over the internet are written to a series different from your other invoices. This split is built at the very start of the document layout; the series of a past document cannot be changed later.

Which details must be present on an internet-sale invoice?

The web address where the sale was made, the payment method, the organization that mediated the payment, the payment date, the tax or identity number of the party that carried the goods, the date the goods were sent, a returns section and a statement that the sale was made over the internet. The paper copy of the invoice also travels with the shipped goods.

How are corporate invoice details collected?

Shopify checkout does not collect tax ID, tax office or legal title by default. If those fields are missing, Uyumsoft treats every order as a final consumer. If you sell to businesses, where those details are collected in the payment flow is solved during setup.

What are credits, and how do they affect the integration?

On Uyumsoft, sending an official document drops credits. When the pack runs out, no new document is issued, and in most setups this happens silently. Credits are not a model where every stock query is billed; they are planned against monthly document volume.

Is stock written from Uyumsoft to Shopify?

It is written when Uyum ERP is open; the catalog's truth then sits in Uyumsoft. There is no stock flow on an e-Dönüşüm contract alone, and the catalog keeps living in Shopify.

Which warehouse's stock is opened to the store?

The decision is made in the ERP setup. Opening only the ecommerce warehouse is the safest path. Writing the sum of more than one warehouse collides with store sales. When the decision is changed later, the catalog and the order flow change too.

Which field are products matched on?

Matching is not built on the title. When ERP is open, barcode or stock code is used. Mixing a pack barcode with a single-sale barcode breaks stock silently.

How do variants sit in Uyumsoft?

The vendor's own text does not describe a native variant model like Shopify's. The practical expectation is a separate stock card for every color and size combination. That is not a rule; it is confirmed with a test record.

Are cancellation and return the same document?

They are not. The cancellation window is short, after that a return invoice. When the window has passed, the correction is made with a new document and the two documents are offset. Sources disagree on the number of days, so a day count is not given.

Is an order written into a closed period?

It is not. If an order that lands near month end sits in the queue while the period closes, the record is refused. The bridge turning that into an alert is part of the setup; otherwise the loss stays silent.

My marketplace invoices already leave from Uyumsoft. Is Shopify set up separately?

It is set up as an extra channel on the same seal; you do not need to pick a separate integrator. The job of setup is that the same order is not documented twice, that the account is not opened twice across channels, and that the credit pool can carry both sources.

What changes if Uyumsoft runs on our own server?

e-Dönüşüm sits in the cloud, no server sits in between. If Uyum ERP is on your own server, a secure access path is opened and the bridge is connected to that address. That step does not exist on cloud ERP.

How long does the integration take?

This is a project calendar, not a setup day. Four things set the time: product discovery, GİB and credit confirmation, account and series matching, and the access path if ERP is in place. On server ERP the first week usually goes to access.

How does a foreign-currency sale land on the invoice?

Shopify can sell in more than one currency; the accounting record enters after conversion into local currency. If which day's rate is used is not set up, reconciliation breaks every month with small differences.

Is the shipping charge added to the invoice?

Whether it is added, and at what rate, is defined during setup. The rate is not assumed; it is seen on a test document. The wrong rate produces a VAT difference at month end.