Shopify Bizim Hesap Integration

Bizim Hesap is a cloud pre-accounting and e-invoice product; Shopify appears by name on its official integration list and the connection is built from the panel. The clearest difference in this category is that the scope has no extra fee: there is no separate charge for the ecommerce integration or the stock and warehouse module. Setup runs step by step from the panel. On two-way stock the system-of-record decision is left to you, the invoice is issued in two steps, and the product's own virtual POS works separately from Shopify payments.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Bizim Hesap integration what is it?

A Shopify Bizim Hesap integration is the connection that keeps store orders, customers, products and stock movements lined up with the pre-accounting side. The aim is to issue the invoice from one place, stop writing the account and stock record a second time, and make the data that goes to accounting match the sale.

The connection is not built by installing an app on Shopify; it is built from the integrations section of the Bizim Hesap panel. Because the product is cloud-based, you do not need a server, a virtual network or a fixed address. Shopify appears by name on the official ecommerce-platform list, but a step-by-step guide written for Shopify has not been published. Because there is no general guide, stores building this connection for the first time usually take support from Nodus Works' Shopify integration and custom app development service.

Once the connection is live, the order lands in pre-accounting, it is invoiced through the customer account, and stock updates with the sale. Because the stock claim is two-way, you have to decide during setup which side is the system of record; if that decision is not made, the two sides overwrite each other's counts.

WHAT SYNCS

What syncs between Shopify and Bizim Hesap

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

Order transfer and bulk invoicing

Orders from the store land in pre-accounting and can be invoiced in bulk in a single action. Whether an automatic trigger tied to order status exists is not documented; you have to define that rule during setup.

e-Invoice and e-archive layout

The invoice is issued through the customer account card and the flow is two-step: the document first becomes an internal record, and turning it into an e-document is a separate action. Knowing that split explains why an invoice you thought was issued never went out.

Two-way stock updates

The product's own definition is two-way: stock movements from retail or online sales can be updated across every channel. That strength turns into risk when a system of record is not chosen.

Product matching and bulk updates

Product data from different platforms is managed and matched in one place, and a bulk product update refreshes every channel from the same screen. Which field the match is built on is not written in official documentation.

Customer accounts and statements

Every invoice runs attached to an account; account transfers, sending a live statement to the customer and user authorization sit on the product's own list. Those capabilities pay off in a pattern where every customer has a separate account.

Collections and bank reconciliation

The product has its own virtual POS service and a large number of bank integrations; bank movements come into the program. Which cash account a store payment writes to is a decision defined during setup.

CONNECTION PATH

From which direction is the connection built?

The path on this product is relatively clean: the connection is built from the product's own panel. Against that, there are three separate paths and their scopes differ in a clear way.

The official path from the panel has the widest scope

Shopify appears by name on the product's own ecommerce-platform list and the connection is started from the integrations section of the panel. Because it is cloud-based, you do not need a server, a virtual network or a fixed address; orders, stock, accounts and invoices enter the same flow.

A Shopify-specific official guide has not been published

The product lists Shopify, but which Shopify permission is requested and where the connection is confirmed is not written down. That gap produces question marks during setup; the steps below are therefore written with screen names.

App Store bridges only carry the invoice

The product has not published a Shopify app of its own. Bridges in the App Store support this product, but their scope is limited to invoices: they do not promise stock, account balances or collections, and they require a separate subscription.

Multi-channel panels are a third layer

Multi-channel panels that manage Shopify together with your marketplaces also connect to this product. On that path, scope and behavior are set by that panel's rules, not the product's, and a separate subscription arrives.

The scope has no extra fee

The ecommerce integration and the stock and warehouse module are not extra paid items; the official text says no account operating fee is charged for any action from integrations through the virtual POS. In the products we compare, ecommerce is a separate subscription, so this is the clearest difference in total cost.

Watch claims about upper-tier plans

A bridge's claim that you do not need to move to Shopify's upper-tier plans is unsourced. Some order fields are known to be shared depending on plan level; that is why you have to confirm which data arrives in your own setup.

SETUP

How is the Shopify Bizim Hesap integration done?

The six steps below cover the full setup, from building the connection in the panel through the first test order. Because there is no official Shopify guide for the product, we give the steps in the order used in practice.

Start the integration from the panel

From the integrations screen under settings in the Bizim Hesap panel, Shopify is chosen as the ecommerce platform and the connection is built from there. Because it is cloud-based, you do not need to prepare a server or a fixed address.

Define store access and confirm the connection

After your store address and access details are entered, the connection is checked. Because which Shopify permissions are requested is not written in official documentation, seeing the first order arrive is the most reliable confirmation.

Set up product matching

Products are matched from a single screen and bulk updates run from there. Which field the match is built on is not written in official documentation; in practice stock code and barcode are the base, so the codes have to be the same and unique on both sides.

Choose the system of record for stock and map warehouses

Because the product's stock claim is two-way, you have to decide which side wins. If you have a physical store or field sales, the system of record should be pre-accounting, because Shopify does not see those movements. In the same step you decide which warehouse's stock goes to the store.

Define account, tax ID and invoice rules

You decide whether every customer gets a separate account or a single retail account is used. Collecting a tax ID at checkout, defining tax rates per product and carrying the shipping charge as a separate service line are also set in this step.

Verify the flow with a test order

Place an order with a single product and see that it lands in pre-accounting, that an account record opens, that stock drops and that the invoice is issued in the right document type. Also check the step where the invoice turns from an internal record into an e-document.

The table below shows which Shopify records map to which counterparts on the pre-accounting side.

What Shopify has	What it maps to in Bizim Hesap
Order	Order record, then invoice
Customer	Customer account
Product	Stock card
SKU	Stock code, the matching key
Barcode	Barcode
Stock	Warehouse quantity, multiple warehouses possible
Shipping charge	Separate service line
Payment	Cash or bank movement
No Shopify counterpart	Tax ID and tax office, document series, account deduplication rule, system-of-record decision

Where are you in the setup?

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

COST

What changes when the scope has no extra fee?

Pricing on this product has two layers: the plan subscription and e-document credits. Credits fall per document and their packs are sold separately; a fourteen-day free trial is also available. Because plans change and tables in third-party roundups can give values that differ from the official source, you need to confirm the current amount on the product's own pricing page.

The clearest difference in the category is scope: the ecommerce integration and the stock and warehouse module are not extra paid items. The official text says no account operating fee is charged for any action from integrations through the virtual POS, and that the stock and warehouse tracking module can also be used without an extra fee. In the products we compare, the ecommerce module is a separate subscription and detailed stock is tied to an upper-tier plan, so the total cost table comes out clearly different here.

The practical meaning is this: the number of items you have to cost on this product is small. Outside the plan subscription and credits there is no third module line, and bank integration is included in the plan. If you choose to use a bridge from the App Store, that bridge's subscription and credits arrive separately; on that path the scope also stays limited to invoices.

How many credits fall by document type is not broken out on the official pricing page, so we do not write a ratio here. If your monthly document count is high, measuring credit use from the first month and picking the pack against that is the soundest path; if you also use e-waybills this item can grow faster than you expect.

STOCK

How is the system of record chosen on two-way stock?

This product's strongest side is stock, and the riskiest side is the same place. When two-way sync is on and which side wins is not defined, the two sides overwrite each other's counts.

Warehouse structure is strong in this band

Multiple warehouses, transfers between warehouses, warehouse by branch or person, critical stock-level alerts, variant stock management and production tracking are officially defined. Even a vehicle can be defined as a warehouse, which is why businesses that sell in the field pick this product.

The claim is two-way

The product's own definition says it updates stock movements from retail or online sales across every channel. That means physical and online sales drop a single inventory and can write it out to the channels.

If no system of record is chosen, the two sides overwrite each other

When two-way writing is on, which side wins a conflict is not documented on the product side. That decision is left to you; if it is not written down, counts break in turns and the only way to fix them is a physical count.

If you have physical sales, the system of record should be pre-accounting

If you sell from a store or in the field, Shopify does not see those movements; making the store the system of record in that structure breaks inventory. If you only sell online, treating the store as the system of record is simpler.

Sync frequency is not documented

How often a stock update lands and how store locations are mapped to warehouses is not written in official documentation. On discount days that interval can be the source of an oversell, so you have to measure it in your own setup.

With several warehouses, which quantity is sent has to be defined

When more than one warehouse exists, whether the store receives total stock or the selected warehouse's quantity is not documented. Sending the total is the riskiest pattern; make it clear during setup which warehouse is opened for sale.

When you set your stock rule you also have to account for marketplace channels: if Trendyol and Hepsiburada sell from the same inventory, the system-of-record decision affects every channel. To watch orders, stock and the invoice flow from one place, look at Station.

INVOICES

How is an invoice issued, and how is it cancelled?

On this product the invoice flow runs through the customer account and is two-step. Not knowing that split is the most common reason an invoice you thought was issued never reached the other side.

The flow runs through the account and is two-step

The invoice is saved by making a sale from the customer account card, then the e-invoice step is run on the screen that opens. So the document first becomes an internal record, and turning it into an e-document is a separate action. On the ecommerce side there is a bulk counterpart: orders can be invoiced in a single action.

Document type follows the buyer's taxpayer status

An e-invoice is issued to a taxpayer in scope, an e-archive to a taxpayer out of scope and to an end consumer. There is no official statement that the decision is made automatically from the tax ID on the screen, so we do not write that as a rule.

If the tax ID is not collected, everyone becomes an end consumer

The Shopify checkout does not collect a tax ID or tax office by default. When those fields are not collected, an end-consumer invoice is also issued to a corporate customer and the account has to be edited by hand.

An automatic trigger is not documented

Which order or payment status triggers the invoice is not written in official documentation. That is why you have to set the rule; issuing a document on an order whose payment is not confirmed creates return-invoice work on cancellation.

The cancellation window is eight days

Issued e-archive invoices can be cancelled within eight days; invoices not cancelled inside that window are treated as approved. The cancellation request is created through the official portal and approved by the other side. Some sources give a different number of days; the official source says eight days.

Internet-sale invoices have their own rules

The invoice series for sales made over the internet has to be separate, and the invoice must carry a returns section and a statement that the sale was made over the internet. Set this split from the start when you build your invoice layout.

On the return side we have to be honest: how a return invoice is produced on this product's screen, and what a partial return on the store maps to, is not written in official documentation. If the eight-day window has passed, the path is a return invoice, not a cancellation, and that document states the original invoice's details; the flow has to be made clear during setup.

ACCOUNTS AND PAYMENTS

How are the account pattern and collections set up?

On the account side the choice is left to you; on the collection side this product has a capability that sets it apart in the category, but its relationship to Shopify is not clear.

The account-deduplication decision is yours

A separate account per customer makes statements and balances meaningful, but at retail volume it swells the list. A single retail account keeps the list clean, and you lose per-customer tracking. There is no official rule on the product side for this choice.

Statements and authorization pay off in a separate-account pattern

Account transfers, sending a live statement to the customer and splitting the rights to view and issue invoices sit on the product's own list. Those capabilities only find a counterpart in a pattern where every customer has a separate account.

A corporate account cannot be opened without the collected fields

A corporate account cannot be opened without a tax ID, tax office and legal title. When those fields are not collected in the payment flow, the account is edited by hand and the invoice is issued after that; if you sell to companies you have to automate this.

The product has its own virtual POS service

This is a capability that sets it apart in the category: the product we compare does not offer a virtual POS and points you to another provider. The critical question is unanswered: whether this virtual POS can be attached to the Shopify checkout is not documented.

A Shopify payment runs through your own stack

If payment in your store is taken through your own payment stack, the product's virtual POS does not come into play. How and to which cash account that collection writes into pre-accounting is a decision defined during setup; if this is not made clear, reconciliation stays on you.

Bank reconciliation is included in the plan

A large number of bank integrations have no extra fee and account movements come into the program. There is no source that payment-stack commission, shipping cost and store commission are written automatically as expenses; make it clear during setup how those items are posted.

COMMON MISTAKES

The most common mistakes in the Shopify Bizim Hesap integration

The nine headings below are the mistakes that come up most often in setup. Some of them are not technical; they come from treating an undocumented behavior as if it were documented.

Not choosing a system of record on two-way stock

When two-way writing is on, which side wins a conflict is not documented. If the decision is not written down, counts overwrite each other and the only way to fix them is a physical count.

Not defining which quantity is sent with several warehouses

Sending total stock to the store is the riskiest pattern; the gap between warehouses comes back as a cancellation. Which warehouse is opened for sale has to be decided during setup.

Not knowing that the invoice is two-step

The document first becomes an internal record; turning it into an e-document is a separate action. When that step is skipped the invoice is thought to be issued, but it never reaches the other side.

Not adding a tax ID field to checkout

When the field is not collected, an end-consumer invoice is also issued to a corporate customer and the account has to be edited by hand for every document.

Not defining an invoice trigger

Because which order status issues the invoice is not documented, you have to set the rule. A document issued on an order whose payment is not confirmed creates return-invoice work on cancellation.

Matching without checking stock codes

Which field the match is built on is not written down, and what happens to an unmatched product is also not documented. If code discipline is not set, there is a risk of a second card for the same product.

Assuming the virtual POS replaces Shopify payments

The product has its own virtual POS service, but whether it can be attached to the Shopify checkout is not documented. If payment in the store runs through your own stack, that feature does not come into play.

Using a single tax rate on a mixed catalog

When reduced-rate products are sent at a single fixed rate, the invoice comes out wrong. Rates have to be defined per product and the shipping charge has to be carried as a separate service line.

Writing internet sales onto the same invoice series

Internet-sale invoices must use a separate series; the invoice must carry a returns section and the required statement. If this split is not set from the start, a retrospective correction is required.

SCENARIO

Three common problems and how they were solved

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

Store and warehouse counts drifting without stop

ProblemCounts tied in the first weeks after setup, then started to drift. Some products stayed on sale in the store while the warehouse was empty; on others the warehouse had stock but the store would not open them for sale.

CauseStock was running two ways, but which side won a conflict had never been defined. When a store sale and a physical-store sale happened at the same time, the two sides wrote over each other's quantity.

SolutionPre-accounting was set as the system of record, because only that side saw the physical-sale movements. Which warehouse's stock would go to the store was defined and a safety buffer was left on fast movers; after one physical count the numbers lined up.

Invoices thought to be issued never reaching the customer

ProblemOrders looked as if they were being invoiced regularly and the accounting records also tied. Against that, corporate customers could not find their invoices in their systems and at month end a request arrived for hundreds of documents.

CauseThe invoice flow was two-step: the document became an internal record, and turning it into an e-document required a separate action. The team treated the first step as the invoice being issued and never ran the second step.

SolutionThe bulk invoicing step for orders was tied to a daily job and the number of documents that turned into e-documents was added to the checklist. Once a tax ID field was also added to the payment flow, corporate invoices started going out in the right document type.

The virtual POS expectation not being met

ProblemHaving its own virtual POS service was decisive when the product was chosen, and it was assumed that store payments would also run through that stack. During setup that expectation could not be met and the payment side had to be replanned.

CauseThe product has a virtual POS service, but whether it can be attached to the Shopify checkout is not documented. Because payment in the store ran through its own payment stack, that feature did not come into play.

SolutionThe payment side was left on the store's own stack and which cash account the collection would write to in pre-accounting was defined. How commission and shipping cost would be posted as expenses was also written down; reconciliation stopped being a hand job.

STATION

Shopify Bizim Hesap integration

Station is the tool we built to watch the order, stock and invoice flow from a single panel. When marketplace channels are added, the accounting side stays at the center.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

How is the Shopify Bizim Hesap integration done?

The connection is built from the integrations screen under settings in the Bizim Hesap panel; Shopify is chosen as the ecommerce platform and store access details are entered. The next steps are setting up product matching, choosing the system of record for stock, defining account and invoice rules, and placing a test order with a single product. Because the product is cloud-based, you do not need to prepare a server or a fixed address.

Does Bizim Hesap have a Shopify app?

It has not published a Shopify app of its own; the connection is not built by installing an app on Shopify, it is built from the product's own panel. Shopify appears by name on the product's official ecommerce-platform list. Bridges in the App Store that support this product belong to independent developers and their scope is limited to invoices.

Is there a Shopify-specific setup guide?

The product lists Shopify, but a step-by-step official guide written for Shopify has not been published: which Shopify permission is requested and where the connection is confirmed is not written down. The steps are therefore written in the order used in practice; the most reliable way to confirm the connection is to see the first order land.

Will I pay an extra fee for the integration?

You will not. The ecommerce integration and the stock and warehouse module are not extra paid items; the official text says no account operating fee is charged for any action from integrations through the virtual POS, and that the stock and warehouse tracking module can also be used without an extra fee. This is the clearest difference from the products we compare, where the ecommerce module is a separate subscription.

How does pricing work?

It has two layers: the plan subscription and e-document credits. Credits fall per document and their packs are sold separately; a fourteen-day free trial is also available. How many credits fall by document type is not broken out on the official pricing page, so we do not write a ratio here; if your monthly document count is high, measuring use from the first month is the soundest path.

I only want to connect invoices. Is there an option?

There is. Bridges in the App Store support this product and issue an e-invoice or e-archive by order status. You have to choose the scope on purpose: those bridges do not carry stock, account balances or collections and they require a separate subscription. The official path from the panel has a wider scope and no extra fee.

Do I have to move to Shopify's upper-tier plan?

A bridge's claim that you do not need to move to an upper-tier plan is unsourced, so we do not give a commitment here. Some order fields are known to be shared depending on plan level; the safest path is to confirm which data arrives in your own setup with the first test order.

Does stock run two ways?

The product's own definition is two-way: it says it updates stock movements from retail or online sales across every channel. That is a strong feature, but which side wins a conflict is not documented; that is why the system-of-record decision has to be made during setup.

Which side should be the system of record for stock?

If you sell from a physical store or in the field, the system of record should be pre-accounting, because Shopify does not see those movements. If you only sell online, treating the store as the system of record is simpler. The critical rule is this: when two-way writing is on and which side wins is not defined, counts break each other in turns.

Are multiple warehouses supported?

They are, and this band is strong: multiple warehouses, transfers between warehouses, warehouse by branch or person, critical stock-level alerts, variant stock management and production tracking are officially defined. Even a vehicle can be defined as a warehouse. Against that, how store locations are mapped to warehouses is not written down.

When I have more than one warehouse, which quantity goes to the store?

Whether the total or the selected warehouse's quantity is sent is not stated in official documentation. Sending total stock is the riskiest pattern, because the gap between warehouses comes back as a cancellation. You have to define during setup which warehouse is opened for sale and leave a safety buffer on fast movers.

How often is stock updated?

Sync frequency is not written in official documentation. On discount days that interval can be the source of an oversell, so you have to measure it in your own setup; a safety buffer that does not open the last few units for sale is also the most practical protection.

Which field are products matched on?

The official source only says product data from different platforms can be managed and matched in one place; which field the match is built on is not written down. Because the stock module works with barcodes, stock code and barcode are the base in practice. The codes have to be the same and unique on both sides.

What happens to an unmatched product?

This is not stated in official documentation, so we do not write a definite behavior. On similar products, a new card being opened for an unmatched product and a duplicate card forming is a known trap; assuming the same risk and setting code discipline before you transfer the catalog is the safest path.

Are variant products supported?

Variant stock management sits as a separate row in the official plan table. Against that, how color and size variants on Shopify map to it, and whether there is a parent-product idea, is not written down. If you work with a variant catalog you have to test this with a trial product before setup.

How is an invoice issued?

The flow runs through the customer account and is two-step: a sale is made from the account card and the invoice is saved, then the e-invoice step is run on the screen that opens. So the document first becomes an internal record, and turning it into an e-document is a separate action. On the ecommerce side there is a bulk counterpart: orders can be invoiced in a single action.

I issued the invoice but the customer did not receive it. Why?

Most likely the second step was not run. On this product the document first becomes an internal record and turning it into an e-document requires a separate click. That is the most common reason the other side does not see the document while the accounting record ties; tying the bulk invoicing step to a daily job closes the problem.

Is the invoice issued as an e-invoice or an e-archive?

The split follows the buyer's taxpayer status: an e-invoice to a taxpayer in scope, an e-archive to a taxpayer out of scope and to an end consumer without a tax ID. There is no official statement that the decision is made automatically from the tax ID on the screen, so we do not write that as a rule; the flow has to be defined during setup.

What is required for the right invoice to be issued to a corporate customer?

The tax ID, tax office and legal title have to arrive with the order. The Shopify checkout does not collect these by default, so when they are not collected every order is treated as an end consumer and the account is edited by hand before the invoice is issued. If you sell to companies, these fields have to be collected in the payment flow.

At what moment is the invoice issued?

Whether an automatic trigger tied to order status exists is not written in official documentation; the known path on the ecommerce side is invoicing orders in bulk in a single action. That is why you have to set the rule. Issuing a document on an order whose payment is not confirmed creates return-invoice work when a cancellation arrives.

Within how many days can an issued invoice be cancelled?

Issued e-archive invoices can be cancelled within eight days; invoices not cancelled inside that window are automatically treated as approved. The cancellation request is created from the documents issued in your name section of the official portal and approved by the other side. Some sources give a different number of days for this window; the official source says eight days.

How is a return invoice produced?

How a return invoice is produced on this product's screen, and what a partial return on the store maps to, is not written in official documentation, so we do not describe a definite flow. The general rule is this: if the eight-day window has passed, the path is a return invoice, not a cancellation, and that document states the original invoice's details.

Is a separate series required for internet-sale invoices?

Yes. The invoice series for sales made over the internet has to be different from your other invoices, and the invoice must carry a returns section and a statement that the sale was made over the internet. Set this split from the start when you build your invoice layout; a retrospective correction is much more painful.

Is a separate account opened for every customer?

This choice is left to you; there is no official rule. A separate account per customer makes statements and balances meaningful, but at retail volume it swells the account list. A single retail account keeps the list clean, and you lose per-customer tracking. The product's capabilities such as account transfers and live statements find a counterpart in a separate-account pattern.

How is the tax rate decided?

How the rate is decided in the ecommerce integration has not been explained in official documentation, so this mapping is a topic that has to be defined during setup. Rates in Turkey differ from each other, so a single fixed rate on a mixed catalog produces a wrong invoice; reduced rates have to be defined per product.

How does the shipping charge land on the invoice?

The shipping charge has to be carried as a separate service line, with its tax. This is not explained in official documentation, but it has to be defined during setup so the invoice total comes out right and the tax declaration is not short. If tax is not applied to the shipping profile on the store side, the declaration stays short.

Does the Bizim Hesap virtual POS replace Shopify payments?

This question does not have a documented answer, and we have to say that honestly. The product has its own virtual POS service, the product we compare does not; but whether it can be attached to the Shopify checkout as a payment method is not written down. If payment in your store is taken through your own payment stack, that feature does not come into play.

How do bank movements and reconciliation run?

A large number of bank integrations have no extra fee and account movements come into the program; cash, checks, notes and credit tracking are also included in the plan. There is no source that payment-stack commission, shipping cost and store commission are written automatically as expenses; how those items are posted has to be made clear during setup.