Shopify Mikro Integration

A Shopify Mikro integration is the bridge that connects product, stock and invoice data in Mikro to Shopify. Mikro has more than one product line (Run, Jump, Fly, Müşavir). The integration API is clearly defined on the Jump line in particular, and access does not come on its own. It is opened with an application form for that product. Setup does not start by making the connection. It starts when you make clear which Mikro product you use and whether your API access is open.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Mikro integration what is it?

A Shopify Mikro integration is the connection that writes your store's orders and stock movements into the customer account, invoice and warehouse records in Mikro. Mikro does not publish a Shopify app of its own. The bridge is an integration tool that runs on Mikro's official integration interface.

Setup starts with access, not with writing code. Mikro opens API access for each product line. You first make clear which of Jump, Run, Fly or Müşavir you use, and whether your API license is active. Setups that skip this step stall at the connection stage with a sign-in error.

Once the connection is working, a Shopify order becomes a customer account movement in Mikro. Stock updates in both directions, and the details of the issued invoice are written back to the order. To choose the right integration tool for your product line, you can get support from Nodus Works' Shopify integration and custom app development service.

DATA FLOW

What syncs between Shopify and Mikro

Six data groups move regularly between Mikro and Shopify. You need to know which part of Mikro each group is read from and written to. An integration built without that stalls on at least one of these six headings.

Transfer of Shopify orders into Mikro

The order is written as a customer account movement through the session the integration tool opens in Mikro. If the buyer is not on record in Mikro, a new customer account card opens first, and the order is posted to that card.

Mikro Shopify stock sync

Warehouse quantity in Mikro is read at set intervals and written to Shopify. A sale on Shopify also drops stock in Mikro. The read is not instant, and the integration tool's setting decides the interval.

Price and campaign transfer

The selling price on Shopify comes from one of the price lists in Mikro. If you do not choose a separate list for internet sales, the discounted price in the store is carried to the site as well.

Product and variant transfer

The item card in Mikro becomes a product in Shopify, and color and size combinations become variants. The barcode is what links the two sides in this conversion.

Shipping and tracking details

The label and the tracking number come from the integration of the carrier you have an agreement with, not from Mikro. The dispatch record created in Mikro moves the Shopify order to shipped status.

Invoice and return flow

The invoice is issued in Mikro and sent to GİB as an e-invoice or an e-archive. A cancellation or a return made in Shopify does not correct the customer account record in Mikro on its own.

STOCK

How is stock in Mikro written to Shopify?

The quantity sitting in a Mikro warehouse and the quantity opened for sale on Shopify are different numbers. If you write stock without calculating that difference, you can sell a product you do not have.

Quantity set aside for an order is not opened for sale

A product set aside or reserved for a customer order in Mikro still appears in the warehouse quantity. The number sent to Shopify is what remains after that reserved quantity is subtracted.

Choosing the warehouses that connect to Shopify

If more than one warehouse is defined in Mikro, only the warehouses opened to internet sales are matched to Shopify locations. Changing this choice after you go live leaves unexplained differences between past movements and today's stock.

Simultaneous orders between two Mikro reads

Stock updates each time the integration tool reads Mikro. If the last unit sells both in the store and on the site between two reads, it is sold twice. A shorter interval makes that less likely.

The barcode is the shared key of both sides

The barcode is what links a Mikro item card to a Shopify variant. A variant whose barcode is written on two cards, or never entered, does not join the stock transfer.

The product a return invoice puts back into stock

When a return invoice is posted in Mikro, the product goes back into sellable stock. If that increase is not transferred to Shopify, the site keeps showing the product in the warehouse as sold out.

MULTICHANNEL SALES

How do the physical store and the site share the same stock?

For brands that have a store, an online order can leave the warehouse or be shipped from a store shelf. For this to show correctly in Shopify, every dispatch point in Mikro has to be defined as a matching location in Shopify.

A sale at the store register, or a return brought to the register, also changes stock on the site. If this movement is not transferred from Mikro to Shopify, the site keeps selling a product the store has already sold.

A single Shopify order can be fulfilled from two different points. Plan during setup that more than one dispatch record can be created on the Mikro side for the same order.

SETUP

How is the Shopify Mikro integration done?

The six steps below cover the full setup, from discovering the product line through the first order landing in Mikro. The first step is specific to Mikro: API access does not come on its own, and an application for that product is required.

Discover your Mikro product line and API access

Mikro has more than one product line: Run, Jump, Fly and Müşavir. The official API documentation is clearly defined for the Jump line in particular, and the integration method can change on the other lines. API access does not come by default, and you request it from Mikro with an application form for that product.

Get your connection and sign-in details

Mikro's integration interface signs in with a company code, an access key of your own, a user code and your password. The session that opens is used for every transfer after that. You get these details from your partner or from the Mikro support line.

Confirm the connection address and version compatibility

Some third-party sources state a different connection address and a "V17 and above" requirement. This does not fully match Mikro's official v16 document. Before setup, confirm with your partner which connection address your Mikro version supports, and do not build on an assumption.

Connect and match the customer account and warehouse

After the session is open, you move to the integration tool. In this step you define which Mikro warehouse will connect to Shopify, and which customer account code new orders will open under.

Define the variant, barcode and price-list design

Color and size combinations in Mikro are matched to Shopify variants through the barcode. Here you also choose which price list belongs to internet sales.

Verify the flow with a test order

Follow the flow from start to finish with a single order. See that the order posts to the right customer account in Mikro and that stock drops on both sides. Also see that the issued invoice's details come back to Shopify.

Where are you in the setup?

Tell us about your catalog and your current Mikro setup, and together we will work out how the Shopify Mikro integration should be built for your product line. 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

AGREEMENT AND ACCESS

Where do you get your Mikro integration details?

The answer to this question in Mikro depends on your product line. The official API documentation (apidocs.mikro.com.tr) defines a sign-in flow for the Jump line in particular. That flow runs with a company code, an access key, a user code and a password. You get these details from your Mikro partner or from Mikro's own support channel.

API access does not come on its own. Mikro grants API use with an application form for each product. If this access is not open on your license, you have to finish that application before setup. Setups that skip this step and buy an integration tool directly meet an unexpected delay at the sign-in stage.

Third-party sources mention a different connection address and a version requirement ("V17 and above"). This does not match Mikro's official v16 document exactly. Ask your partner or the Mikro support line which connection address works on which version, and do not assume the answer. That check at the very start of setup keeps you from losing time.

COMMON MISTAKES

The most common mistakes in a Shopify Mikro integration

Leaving API access until after the quote

Because Mikro API access requires an application, starting that process after the integration tool is chosen ties the setup calendar to an uncertain waiting period.

Buying an integration tool before confirming the product line

An integration package bought without knowing the API difference between Run, Jump, Fly and Müşavir tries to connect to the wrong connection address during setup.

Opening the store price list to the site

If the list defined in Mikro for the store is also attached to internet sales, the campaign at the register and the staff discount land on the Shopify price.

Treating a variant with no barcode as transferred

A variant whose barcode was never entered, or that repeats on another card, does not match Mikro. That variant's stock is never updated in Shopify, and the gap shows only when a product sells with no stock.

Leaving a cancelled order open in Mikro

An order cancelled in Shopify does not reverse the customer account movement in Mikro on its own. If that link is not built, the customer's account balance shows a debt that does not actually exist.

Trusting a third-party connection detail without checking

A connection address or version detail that conflicts with the official documentation has to be confirmed before setup. If it is not, going live can end in a sign-in error.

VARIANT AND BARCODE

How is the color and size matrix translated into Shopify?

In Mikro v17 the variant structure changed. Color and size were taken off the item card and moved into a separate variant structure. On a setup upgraded from v15 or v16, building on the old structure causes the record to be refused, so confirm which version you are on first.

Matching on the barcode side uses the barcode definitions in Mikro. Each barcode record is tied to one color and size combination. If the variant barcode in Shopify does not match that combination exactly, the variant stays out of stock sync.

INVOICES

How is an internet-sale invoice issued in Mikro?

On Mikro v15 and later, a different e-invoice series can be defined per branch. Tying your internet-sales channel to a separate branch is the standard way to separate that invoice series from in-store sales.

The branch code is opened first on the definition card

On the branch definition screen (screen 501800) a new branch code is defined, and your internet-sales channel is tied to that branch.

The same branch code is matched in e-Mikro Portal

On the Portal tab "Hesap bilgileri > Şubeler" (Account details > Branches), the same code is defined, and the e-invoice series for that branch is set there.

The invoice uses the series of the branch that enters it

You have to sign in with the branch code of the branch the invoice will be entered for. An invoice entered from the wrong branch comes out on the wrong series.

STATION

Shopify Mikro integration

Station is the tool we built to run the stock, price, order and invoice flow from a single panel. When marketplace channels are added to the store connected to Mikro, you also manage from one place which branch series invoices each order.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

Does Mikro have an official Shopify app?

No. Mikro does not publish a Shopify app of its own, and the connection is built with a third-party integration tool that runs on Mikro's official integration interface.

Which Mikro product line fits a Shopify integration best?

The official API documentation is clearly defined for the Jump line in particular. If you use Run, Fly or Müşavir, the integration method can change, so confirm it with your partner.

Do I need to pay a fee for API access?

API access is opened through Mikro's application process for each product. Whether that process has a fee, and what its terms are, should be confirmed with your partner or the Mikro support line.

I moved to v17. Why did my old integration break?

In v17, color and size moved off the item card into a separate variant structure. An integration built on the old structure can meet a refused record after this change, so confirm that your integration tool supports the v17 variant structure.