Shopify Logo Integration

Logo is not a single system, and how the integration is built changes from start to finish with which Logo product you use: Tiger and Go run on your own server, İşbaşı sits in the cloud. On the installed side a secure access path and a connector layer sit in between, on the cloud side they do not. The two paths are set up separately. Which license you need changes with the Logo product you use, the connector runs more safely when it is built from the service layer instead of the database, and an internet-sale invoice has rules of its own.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Logo integration what is it?

A Shopify Logo integration is the connection that keeps store orders, customers, products, stock and price lined up with Logo. Logo stays at the center: the order comes from the store into Logo, stock and price go from Logo to the store and the invoice is issued in Logo.

Setup starts by discovering which Logo product you use. On installed products a secure access path is opened to your server, the required license is confirmed and the connector layer is built; on the cloud product none of those steps exists and the connection runs through the vendor's own ecommerce integration. To make clear which path to follow for which Logo product, Nodus Works' Shopify integration and custom app development service makes that discovery for you.

Once the connection is live, daily work runs from one place: the order lands in Logo as a slip or an invoice, a customer account opens, stock and price are written from Logo to the store and the document comes out of Logo's own numbering layout. A separate invoice series must be defined for internet sales.

WHAT SYNCS

What syncs between Shopify and Logo

Once the connection is live, orders, customers, products, stock, price and invoices become parts of the same flow. The six headings below cover the questions that come up most often in a Shopify Logo integration.

Transfer of Shopify orders into Logo

When the order is created in the store it is written into Logo. Whether the order lands as a slip or directly as an invoice is decided during setup; that decision also sets how returns and cancellations are met.

Opening and matching a customer account

The buyer's details turn into a customer account card; if a card already exists it is matched to that, otherwise a new card is opened. Which field the match is built on is critical, because a match set wrongly produces a second card for the same customer.

Item-card and price transfer

Product data and price are written from Logo to the store, so the catalog's truth sits in Logo. Which price list is attached to the store is the critical setup decision; if a wholesale or special list is attached, the wrong price lands on the site.

Stock sync

Quantity is written from Logo to the store and on the Tiger side it can run with a multi-warehouse split. Which warehouse, or the total of which warehouses, is opened to the internet is defined during setup.

e-invoice and e-archive

The document is issued and sent in Logo's own e-invoice module; the number and series come from Logo's document numbering layout. A separate series must be defined for internet sales.

Cancellation and return flow

Cancellation and returns are managed with slips on the Logo side. That a return and a cancellation are not the same thing, and which one applies depends on the age of the document, has to be made clear during setup.

TWO SEPARATE WORLDS

Which Logo product do you use?

The answer to this question sets the whole project. The only thing installed products and the cloud product share is the brand name.

On the cloud product Shopify is supported by name

The vendor's own site lists Shopify by name in the scope of the cloud pre-accounting product's ecommerce integration. Among the seven pre-accounting and ERP systems this is the only one whose vendor text lists Shopify by name; setup runs through the vendor's own integration.

Installed products sit on your own server

Tiger and Go run on your own server and have no address Shopify can reach. That is why two things sit in between: a secure access path and a connector layer that talks to both sides. The first week of the project often goes to this step.

An extra license may be required on the installed side

Two independent integrators write that a service-layer license is required for Tiger and a database-use license on the Go side. We could not confirm this on the vendor's own page, so we do not write it as a rule: you have to confirm it with your partner before a quote.

There is no Logo app of its own in the App Store

There is no solution published under the Logo name in the App Store; apps that point at Logo belong to independent developers and their scope is built around invoices. So a separate design is required for the order, stock and price flow.

The invoice is issued in Logo on both products

The document is produced and sent in Logo's own module; a third sealing firm does not sit in between. On the cloud product the e-archive pack is a separately purchased item, so it has to be added to the cost plan.

When the server goes down the flow stops

On an installed product the integration depends on your server staying up: when the server goes down, the network drops or a local update breaks the connector, sync stops. This is a maintenance load cloud systems do not have.

The practical result is this: if you use the cloud product the project is a settings job, if you use an installed product it is an infrastructure job. Quote, timeline and the ownership line are built on this split; projects that plan the two as the same work stall in the first week.

SETUP

How is the Shopify Logo integration done?

The six steps below cover the full setup. The second and third steps only apply to installed products; if you use the cloud product, the vendor's own ecommerce integration comes into play instead of those two steps.

Make it clear which Logo product you use

Discover whether you use an installed product or cloud pre-accounting, your version and which modules are open. Every timeline given without this information is a guess; the setup path splits in two on this answer.

Confirm the license status with your partner

Ask the partner you reach through logo.com.tr whether an extra license is required for service-layer or database access on an installed product. This is the number-one source of surprise cost on the project.

Set up server access and the connector method

On an installed product a secure access path is opened to your server and which technique the connector will run on is chosen: the product's service layer or the database directly. The service layer looks slower but is preferred because it runs the application's own validations.

Define item-card and customer-account matching

Define which field products match on, how variants will sit in Logo and how customers match to a customer account. Trying a single product and seeing how the record opens, before the decision is made, is the safest path.

Choose the price list, warehouse and invoice series

Decide which price list will be written to the store, which warehouse's stock will be opened and which series will be used for internet sales. Tax rules and how the shipping charge lands on the invoice are also defined in this step.

Verify the flow with a test order

Place an order with a single product and see that the order lands in Logo with the right document, that the customer account opens correctly, that stock drops in the store and that the invoice is issued on the right series. Then return the same order and check the reverse flow.

The table below shows which Shopify records map to which counterparts on the Logo side.

What Shopify has	What it maps to in Logo
Order	Order slip or sales invoice
Customer	Customer account card
Product	Item card
Variant	Defined during setup, no native counterpart
SKU	Stock code, the expected matching key
Price	The value on the attached price list
Stock	Quantity of the selected warehouse or warehouses
Tax	The rate on the item card and the setup rules
Return	Return slip or return invoice
No Shopify counterpart	Tax ID and legal-title fields; invoice-series choice

The variant row in the table is this project's riskiest decision. Because the variant idea is not native in Logo the way it is in Shopify, in practice every variant is expected to be a separate item card; but that is an expectation, not a published rule. If you work with a color and size matrix, the decision has to be made on day one because it affects your whole catalog.

Where are you in the setup?

Tell us about your catalog and current setup, and we will work out how the Shopify Logo 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

CONNECTOR METHOD

Should the connector run on the service layer or on the database?

On installed Logo products the connector runs on one of two techniques: through the product's own service layer, or directly at database level. Both are used in the field and both work; against that, their risks are not the same. Because this question is not asked at the quote stage, we see that most brands do not know which method they run on.

A connector that writes directly to the database is fast, because it skips the application layer. That is exactly the problem: Logo's own validations, duplicate checks and business rules do not run. Also, if the table structure changes on a version upgrade the connector breaks silently; records stop going out and no error appears on any screen. This kind of break is usually noticed at month close.

A connector that runs on the service layer looks slower but runs the application's own rules: a missing field is refused, a duplicate record is blocked, an error comes back. Because the real risk in an integration is not that data does not go, but that it goes wrong and no one notices, this behavior is a safety gain, not a slowness.

Whichever method you choose, the queue has to be visible. When the server goes down, the network drops, a license expires or the accounting period closes, records wait in the queue. A setup that does not raise an alert when the queue errors can run for weeks on missing data; the only thing that makes you notice is a report that does not tie at month end.

INVOICES

How is an internet-sale invoice issued in Logo?

The document is produced in Logo's own module; there is no intermediary on this side. Against that, internet sales have their own rules that come from regulation, and those rules are different from your store sales.

The internet-sale series has to be separate

The series of invoices for sales made over the internet must be different from your other invoices. So your Shopify orders cannot be written to the same series as store or wholesale sales; this layout is set at the very start, the series of past documents cannot be changed.

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 ship date, a returns section and a statement that the sale was made over the internet must be present. Those fields filling in depends on the transfer reading them from the order.

The paper copy goes with the goods

So the returns section can be filled in, the paper copy of the invoice is expected to go with the shipped goods. This rule changes your packing station, not accounting: the label and the invoice output have to be taken in the same step.

Shopify's own document is not an invoice

The order summary Shopify produces is not treated as a valid invoice in Turkey; the legal document always comes from Logo. The aim of the integration is not to send the customer an output, it is to produce a document in Logo on the right series and at the right rate.

The tax rate and the shipping line are defined separately

The rate is read from the item card, but tax rules are also defined in the integration setup. Whether the shipping charge is added to the invoice as a line, and what its rate will be, is also decided in this step.

The cancellation window is short, after that a return invoice

An issued document can only be cancelled inside a set window; after the window the correction is made with a return invoice and the two documents are offset. Sources disagree on the number of days, so we do not give a day count here, but that the window is short is certain.

MATCHING AND MULTICHANNEL

What happens if a marketplace also writes to the same Logo?

Most brands that use Logo build the marketplace connection first. When Shopify is added, two channels writing to the same records produce new risks; on connectors that run at database level this risk is even larger.

The match is built on stock code and customer account

Connectors match the product on stock code and the customer on the customer account card. The code has to be identical on both sides; if it is different, a second item card is opened for the same product and the stock report shows no channel's truth.

The risk of a separate item card per channel

If the same physical product is recorded with a different code on the marketplace and in your store, two cards open in Logo. Lining up the existing codes before a new channel is added is the most tedious but most valuable setup step.

A database connector can open a duplicate slip

Connectors that write directly to the database can skip Logo's own duplicate checks, so the same order can open a slip twice. On connectors that run on the service layer those checks stay in play.

The same warehouse's stock is reserved twice

If two channels sell from the same warehouse, the quantity can drop twice or not drop at all. Holding the real stock in one place and writing it from there to every channel is the only lasting way to prevent a collision.

Marketplace deductions are not the sales amount

Because commission and shipping deductions are taken from the marketplace payout, the sales amount written into Logo and the amount that lands in the bank are not the same. How this difference is recorded has to be defined from the start.

The period lock applies to every channel

After the accounting period closes, no record can be opened in that period. If orders that land near month end sit in the queue while the period closes, the record is refused; that is why emptying the queue before the close hour is made a rule.

If your Trendyol and Hepsiburada connections already write to Logo, adding Shopify is not adding one more channel, it is reviewing the record layout again. You can review Station to watch the order, stock and invoice flow from a single panel.

CHECKLIST

What you need to confirm before you request a quote

There is no detailed public technical document for ecommerce integration on the Logo side; most of the information on data direction comes from integrator pages. The headings below are the topics that have to be confirmed with your partner before a quote.

Product and version

Do you use an installed product or cloud pre-accounting, what is your version and which modules are open? The setup path splits in two on this answer; a timeline given without this information is a guess.

Whether an extra license is required

Take in writing from your partner whether an extra license is required for service-layer or database access. Two independent integrators write that it is required; it could not be confirmed on the vendor's own page.

The connector's method

Does the firm giving the quote run on the service layer or on the database? When this question is not asked, the brand does not know which method it runs on and does not understand why it breaks on a version upgrade.

Who owns server access

Who will build the secure access path and who will step in when it drops? On an installed product this is infrastructure work and the ownership line has to be written in the contract.

What a variant maps to

Whether a Shopify variant will be a separate item card is not clear in any source. If you work with a color and size matrix, you have to make this decision on day one.

Price-list and warehouse choice

Which price list will be written to the store and which warehouse's stock will be opened is defined during setup. If the wrong list is attached, the wrong price lands on the site.

Which document the order lands on

An order slip or a direct invoice? This decision also sets how returns and cancellations are met, so it is made from the start.

The steps of the return flow

Which slips a return and a cancellation produce is not described in an official document. You have to see the flow by returning the test order.

Queue alert

Will an alert be raised when a record is refused? A period lock, a license expiry and a server outage leave records sitting silently in the queue; in a setup with no alert, missing data is noticed at month end.

SCENARIO

Three common problems and how they were solved

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

Sync that stopped after a version upgrade

ProblemA version upgrade was done on the Logo side at year end and the following week stock in the store looked frozen. Orders kept landing but stock and price updates were not coming; because no error appeared on any screen, the problem was only noticed when oversells started.

CauseThe connector was running directly at database level. The table structure changed in the upgrade so the read broke silently; because the application layer was not in play, neither a validation nor an error message was produced.

SolutionThe connector was moved to the product's service layer and an alert was set up for records that errored in the queue. Testing the integration against a separate checklist before an upgrade was made a process, so the same silent break did not repeat.

The wrong price landing on the store

ProblemAfter the connection was built, prices in the store looked below expectation and sales ran at those prices for a few days. The gap only appeared in the mid-month profit report.

CauseThe price list attached to the store was not the retail list, it was a list defined for wholesale customers. Because Logo has more than one price list, the list chosen during setup had not been confirmed.

SolutionThe list that would be written to the store was made clear and only that list was transferred. A small end-of-day checklist was built for the accuracy of the price transfer; which list would apply in campaign periods was also written down.

The same order landing as a slip twice

ProblemAfter Shopify was added on top of the marketplace connection, duplicate slips started appearing in Logo. Account balances swelled, stock dropped twice and month close spread from a one-day job into a week.

CauseTwo connectors were reading the same orders separately and the connector that ran at database level was skipping Logo's own duplicate checks. The same product was also recorded with a different stock code on two channels, so second item cards had been opened.

SolutionWhich connector would write which channel's orders was made clear, stock codes were lined up on both sides and duplicate cards were merged. The write was moved to the service layer so Logo's own checks stayed in play.

STATION

Shopify Logo 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 Logo, you see the duplicate-record risk here.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

How is the Shopify Logo integration done?

Setup starts by discovering which Logo product you use, because the path splits in two from there. If you use an installed product the required license is confirmed, a secure access path is opened to your server and the connector layer is built; if you use cloud pre-accounting the connection runs through the vendor's own ecommerce integration. The next steps are defining item-card and customer-account matching, choosing the price list, warehouse and invoice series, and placing a test order with a single product.

Does Logo have a Shopify app of its own?

There is no solution published under the Logo name in the App Store. Apps that point at Logo belong to independent developers and their scope is built around invoices, so they pull the order and issue a document. A separate connector design is required for the full order, stock and price flow.

Does Logo İşbaşı support Shopify?

The vendor's own site lists Shopify by name in the scope of the cloud pre-accounting product's ecommerce integration. This is the only example among the seven pre-accounting and ERP systems we reviewed whose vendor text lists Shopify by name. Because the screen names and step order of the setup have not been published, you have to confirm that detail with Logo.

How is Logo Tiger connected to Shopify, and is a server required?

Tiger runs on your own server and has no address Shopify can reach; that is why a secure access path and a connector layer that talks to both sides sit in between. Building the access path is infrastructure work: when the server goes down, the network drops or a local update breaks the connector, sync stops. Cloud products have none of this maintenance load.

Does a Shopify integration work with Logo Go?

It does, but Go is also an installed product; so server access and a connector layer are required, as with Tiger. Integrators also write that a database-use license is required on the Go side. We could not confirm this license requirement on the vendor's own page, so we suggest you confirm it in writing with your partner before a quote.

Which license is required for a Logo Shopify integration?

Two independent integrators write that an extra license is required on installed products: a service-layer license on the Tiger side, a database-use license on the Go side. Because we could not confirm this on the vendor's own page, we do not write it here as a definite rule. The practical advice is clear: take the license status in writing from your partner before you request a quote, because this is the number-one source of surprise cost on the project.

Should the connector be built from the database or from the service layer?

Both are used in the field but their risks are not the same. A connector that writes directly to the database is fast, against that it skips Logo's own validations and duplicate checks; if the table structure changes on a version upgrade it breaks silently. A connector that runs on the service layer looks slower but refuses a missing field, blocks a duplicate record and returns an error. Because the real risk in an integration is not that data does not go but that it goes wrong and is not noticed, the service layer is preferred.

Do Shopify orders land in Logo as an invoice or as an order slip?

Both are possible and this is a decision made in the setup. The importance of the decision is this: in a design where the order turns directly into an invoice, a document is also issued on an order that will be cancelled and the correction requires a return invoice. In a design that runs through a slip, the document can be issued at the moment of dispatch; the return and cancellation flow is built accordingly.

How are stock and price transferred from Logo to Shopify?

The catalog's truth sits in Logo and stock and price are written from Logo to the store. Two decisions are made during setup: which price list is attached to the store, and which warehouse, or the total of which warehouses, is opened to the internet. Attaching the wrong list is the most common mistake; if a wholesale or special list is attached, the wrong price lands on the site.

Which field are products matched on?

Connectors match the product on stock code and the customer on the customer account card; the code has to be identical on both sides. When a transfer is run before the codes are lined up, a second item card is opened for the same product and the stock report shows no channel's truth. Because the source of this information is integrator documentation, we suggest you confirm it with a test record during setup.

How do Shopify variants sit in Logo?

There is no published definite answer and we do not invent one. Because the variant idea is not native in Logo the way it is in Shopify, in practice every variant is expected to be a separate item card, but that is an expectation. If you work with a color and size matrix, this decision has to be made on day one because it affects your whole catalog, your stock reports and your invoice lines.

Does a customer account open automatically?

It can: the buyer's details turn into a customer account card, and if a card already exists it is matched to that. The point to watch is duplication: when the same person arrives with a different email or phone a second card opens and merging is done by hand. What rule will be set for customers who shop without opening an account also has to be decided from the start.

Is a separate integrator required for e-invoice in Logo?

It is not; the document is issued and sent in Logo's own e-invoice module, a third sealing firm does not sit in between. The number and series come from Logo's document numbering layout. On the cloud pre-accounting side the e-archive pack being a separately purchased item has to be added to the cost plan.

Is a separate series required for internet-sale invoices?

Yes. The series of invoices for sales made over the internet must be different from your other invoices, so your Shopify orders cannot be written to the same series as store or wholesale sales. This layout is set at the very start; because the series of past documents cannot be changed later, there is no correction path.

Which fields are required 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 must be present. The paper copy of the invoice is also expected to go with the shipped goods; this directly affects your packing flow.

Is Shopify's own invoice valid in Turkey?

No. The order summary Shopify produces is not treated as a valid invoice in Turkey; the legal document always comes from your accounting system, that is from Logo. That is why the aim of the integration is not to send the customer an output, it is to produce a document in Logo on the right series, at the right rate and with the required fields filled.

How is the invoice of a returned order corrected?

It depends on the age of the document. An issued document can only be cancelled inside a set window; after the window the correction is made with a return invoice, not a cancellation, and the two documents are offset against each other. Sources disagree on the number of days, so we do not give a day count here. During setup, return and cancellation have to be defined as separate flows; otherwise the account balance and the sales report drift.

How does the shipping charge land on the invoice?

Whether the shipping charge is added to the document as a separate line is defined during setup. Because the tax rate of the shipping line can differ from the product tax, the rate has to be confirmed with a test document instead of an assumption. On a return the same line is also dropped with its tax; if it was not charged to the customer it stays as an expense.

Why do orders that land at month end not go into Logo?

After the accounting period closes, no record can be opened in that period. If an order that lands near the last day of the month sits in the connector queue while the period closes, the record is refused and in most setups this happens silently. The fix is two-step: raise an alert for records that error in the queue, and make emptying the queue before the close hour a routine.

What happens when our server goes down?

On an installed product the integration depends on your server staying up: when the server goes down, the network drops or a local update breaks the connector, sync stops. Records wait in the queue and in a setup where the queue is not visible this goes unnoticed for weeks. That is why the question of who steps in on an access outage has to have an answer in the contract.

What happens if Trendyol and Shopify write to the same Logo?

There are three risks. If the same physical product is recorded with a different stock code on two channels, a second item card opens; the same customer is recorded as two accounts; if two connectors read the same order separately a duplicate slip forms. Because connectors that run at database level can skip Logo's own duplicate checks, this last risk is larger there.

How do marketplace deductions enter Logo?

Because commission and shipping deductions are taken from the marketplace payout, the sales amount written into Logo and the amount that lands in the bank are not the same. Whether this difference is recorded as an expense or as a sales discount is decided with your accountant; if it is not defined, bank reconciliation is corrected by hand every month.

Can I work with multiple warehouses?

On the Tiger side you can work with a multi-warehouse split and which warehouse, or the total of which warehouses, is opened to the store is defined during setup. The point to watch here is the same warehouse being sold by more than one channel: the quantity can drop twice or not drop at all. Holding the real stock in one place and writing it from there to every channel is the most lasting solution.

I sell in a foreign currency. How do the records enter?

Shopify can sell in more than one currency; on the Logo side the record enters after conversion into local currency. If which day's rate is used is not defined during setup, reconciliation breaks every month with small differences. Because there is no published rate policy on this topic, the decision has to be made on the project and written down.

How long does the integration take?

Because the duration depends on which Logo product you use, we do not give a single answer. On the cloud pre-accounting side the project is a settings job; on an installed product, license confirmation, server access and connector setup are added so it turns into an infrastructure job. A realistic timeline can be produced after the product and version are discovered and the license status is clear.