Shopify n11 Integration

To sell your Shopify products on n11, the two systems have to keep talking to each other. n11 does not publish an official Shopify app, so an integration tool builds that connection. Setup starts with the seller application and closes with your first order. In between, the product, stock, price, and order flows are each built separately, and n11's catalog rules cut into that flow.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify n11 integration what is it?

A Shopify n11 integration is the connection that keeps your products, stock quantities, prices, and incoming orders aligned in both systems. Because n11 does not publish an official Shopify app, that connection is built with an integration tool, and the tool takes over the copying work between the two panels.

Setup starts once your n11 seller application is approved. After approval you create a connection account in Satıcı Ofisi, map categories and required attributes, build the variant setup around model codes, and define your price and stock rules. When the variant setup around model codes does not fit the standard template, Nodus Works' Shopify integration and custom app development service builds a custom structure for that setup. The last step is a test order placed with a single product.

Once the connection is live, day-to-day work runs from one place. Orders placed on n11 land in Shopify, stock drops on both sides when a product sells, and you manage campaign prices through a rule instead of rewriting them product by product.

WHAT SYNCS

What syncs between Shopify and n11

Once the connection is live, product data, stock, prices, orders, shipping, and invoices sit in the same flow. The six headings below cover the questions that come up most often in a Shopify n11 integration.

n11 product transfer and sync

Your Shopify products are sent to the n11 catalog after category and required-attribute mapping is in place. When product data changes later, the same flow carries the update.

Shopify n11 inventory sync

When a sale happens on one channel, the other channel's quantity drops as well, so the two stores do not sell the last unit twice. You decide which Shopify location is opened to n11.

Shopify n11 price sync

The n11 price does not have to match the Shopify price, and in most cases it should not. You define a separate rule that includes commission and any shipping share, and both sides update from that rule during campaign periods.

n11 order transfer

Orders placed on n11 are written into Shopify, so you work from the same list as the warehouse. You do not need to move between two panels during the day for shipping, invoices, or returns.

n11 shipping template and label

n11 ties shipping data to a per-product delivery template, and the parcel label is generated in Satıcı Ofisi. You cannot send a product without a template, so this step stays inside setup.

n11 invoice flow

You issue the invoice in your own e-archive or e-invoice system; n11 asks for that invoice to be attached to the order. The integration only makes sure it matches the right order.

FEATURES

Bulk updates, mapping, and multiple stores

Once a catalog passes a certain size, editing products one by one stops being realistic. Bulk updates, category mapping, and multi-store management are therefore part of the setup, not extras.

Bulk stock and price updates

You can filter price, stock, and shipping templates by category and update them in one pass. When you open a campaign you define the rule once instead of rewriting hundreds of rows by hand.

Bulk price updates
Fast stock changes
Campaign management

Managing multiple n11 stores

If you have more than one n11 store, you can run all of them from a single Shopify inventory. Each store keeps its own product list, the stock pool stays shared, and you can set a separate price rule per store.

Control from one panel
Shared stock pool
Central management

n11 category and attribute mapping

Your Shopify category is bound to n11's lowest-level category, and that category's required attributes are filled before a product is sent. A missing required attribute blocks the send, so the mapping has to be right from the start.

Automatic categorization
Attribute mapping
Matching existing products

SETUP

How do you set up a Shopify n11 integration?

The six steps below cover the full setup, from the seller application through the first test order. Most of the work happens in n11 Satıcı Ofisi, so you need an account with access to the panel; on the Shopify side it is enough for the store to be live.

Open your n11 seller account

The application is submitted at magazam.n11.com, and your documents are uploaded from the Document Management section of the panel. n11 also asks you to sign and upload the seller agreement, so this step may not finish in a single session.

Create your connection account

In Satıcı Ofisi you open My Account, go to the API Accounts screen, and create a new account. Your key is shown on screen, but the password is sent to the store's registered email, so you need access to that inbox.

Map categories and required attributes

When you pick a category at the lowest level, that category's required attributes are listed and all of them have to be filled. On some attributes you can type a value that is not on n11's list; on others only the listed options are valid.

Set up the model code and variant structure

n11 shows rows that share the same model code as options on a single product page. Giving every variant of a Shopify product the same model code keeps color and size from splitting into separate pages.

Define the price, stock, and delivery rule

Instead of sending the Shopify price as-is, set a channel price that includes commission. Product sends also ask for a shipping template and a preparation time, so those two fields have to be defined up front.

Confirm the flow with a test order

Place an order with a single product and check that it lands in Shopify, that stock drops, and that the invoice is attached to the order. If those three work, you can open the rest of the catalog.

The table below shows which n11 fields your Shopify fields map to, using the names you see in the panel.

What you have in Shopify	What it maps to on n11
Title	Product name
SKU	Seller stock code
Product group	Model code, keeps variants on the same page
Price	n11 sale price
Compare-at price	Market sale price
Inventory	Sellable quantity
Image	Product images
Category	Lowest-level category
Barcode	Not required, used for catalog matching
No Shopify field	VAT rate, shipping template, and preparation time

The last row is the part of setup that is missed most often. VAT rate, shipping template, and preparation time are fields n11 asks for that Shopify does not carry; you define those three values once on the integration side.

Where are you in the setup?

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

SELLER ACCOUNT

What do you need to become an n11 seller?

To sell on n11 you need to own a company, and a sole proprietorship is enough. A store cannot be opened with an individual account, so the integration is built on top of that company account. Opening a store is free; you only pay commission when a sale happens.

Becoming an n11 seller as a sole proprietorship

A tax certificate, a signature declaration, and an activity certificate are at the top of the document list. You also need a commercial bank account opened in the company's name; a personal account is not accepted.

Becoming a seller as a limited or joint-stock company

Alongside the tax certificate, n11 asks for a signature circular, the trade registry gazette, an activity certificate, and a KEP address. The list changes by company type, so the headings on the application screen are the ones that count.

Uploading the seller agreement

Besides the other documents, n11 asks you to upload a signed seller agreement. If this step is skipped, the application does not move to review even when the rest of the file looks complete.

The current document list is always on the application screen at magazam.n11.com. Seller approval, building the connection, and products appearing in the store are separate processes, so the timeline should not be tied to a single date.

Stage	How long it takes	Note
Seller application approval	1 to 7 business days	Complete documents move faster; missing documents stretch it
Opening the connection account	Same day	The password goes to the registered email, so that inbox must be ready
Building the connection	Same day	Short if you are using a ready-made tool
Products appearing in the store	A few days	Catalog approval varies by product count and category
Steady sales	The first weeks	Price, preparation time, and store score start to matter here

PRICING

How does n11 commission show up in the price?

n11 takes a commission on every sale by category, and that rate changes from period to period. You see the current rate by category in your seller panel, and your price rule is built on that value.

If you send the Shopify price to n11 as-is, commission comes straight out of your margin. Instead you set the channel price as a rule: commission, any service fee, and a shipping share are added on top of the Shopify price. Once the rule is defined you do not have to write a price on every product.

n11 also asks for a VAT rate per product on the send. Shopify does not carry that field, so the value has to be defined on the integration side. If you have product groups on different VAT rates, setting that split up front is easier than fixing it later.

CATALOG

Where do n11 catalog rules diverge from Trendyol?

If you arrive at n11 with habits built on Trendyol, the catalog is the first place that surprises you. The fields that identify a product, how a variant is built, and how approval works are different on the two marketplaces.

A barcode is not required on n11

A product without a barcode can still be sent to n11; the barcode is only used to match the catalog. On Trendyol a row without a barcode does not even enter review, so you cannot run the two channels from the same checklist.

The model code defines the variant

Rows that share the same model code appear as options on a single product page. Whether color opens a separate page depends on the category rule, so the model code has to be assigned consistently.

Some attributes accept a free value

On some required attributes n11 accepts a value that is not on the list; on others it only uses its own list. Which attributes fall into which group changes by category, so mapping is built category by category.

A catalog match waits for your approval

If the barcode you send matches a record in the n11 catalog, the product moves to waiting for seller approval without looking at attributes. Those products do not go on sale until they are approved, so that part of the list has to be checked separately on setup day.

Tracking product statuses

n11 keeps a product in separate statuses such as approved, in catalog review, pending, rejected from catalog, and action required. A send-completed message does not guarantee any of those statuses, so the result has to be read row by row.

Products left outside the listing limit

When your store's listing allowance is full, a product is marked as outside the limit and does not appear in the store. Opening the catalog in groups instead of all at once makes it easier to see which products dropped for that reason.

n11 also asks for product safety information as part of the product send. Those fields are not standard in Shopify, so collecting manufacturer and responsible-person details before setup keeps half the catalog from coming back with missing information.

STOCK

Why does stock collide, and how do you prevent overselling?

A stock change does not hit n11 instantly; it first joins a queue. A message that the system received the request does not mean the product was updated, so setups that never follow the result end up with oversells and cancellations.

The update does not land instantly

The new quantity you send joins a queue and is processed when its turn comes. If the old quantity is still showing on n11, that queue is the first place to look.

Two channels sell from the same stock

If Shopify and n11 sell from the same warehouse, the last unit can sell on both sides. In that case one of the orders turns into a cancellation, and the cancellation hits your store score.

Writing stock on a product still in review

A product that has not finished catalog approval does not appear in the store, so stock written on it does nothing. Treating those rows as on sale leaves you holding channel stock that does not exist in Shopify.

Writing stock from a multi-location Shopify setup

Sending the sum of every location makes unsellable units appear on n11. Which locations are opened to the channel is a separate decision.

Cancellations and returns restore stock

A product cancelled or returned on n11 goes back into sellable stock. If that movement is not written to Shopify, the two quantities drift apart over time.

Hiding the last few units from the store

Not showing the last few units on n11 at all reduces your sellable stock, but it also lowers cancellation risk. The cost of a cancellation and a score hit is usually higher.

Overselling turns into a cancellation, and a cancellation hits your store score. On Trendyol and Hepsiburada barcode, commission, and approval run on different rules, so writing the same stock rule to every marketplace leaves one channel exposed. If you are opening a second channel next to n11, take a look at Station to manage products, stock, prices, and orders from one panel.

OPERATIONS

What happens after an order arrives?

The order is placed on n11 and the integration writes it into Shopify. From there the work is packing, shipping, invoicing, and returns. Most of those steps follow n11's own rules, so they do not line up one-to-one with the habits you built on the Shopify side.

The shipping template is set with the product

n11 keeps shipping data on the delivery template tied to the product, not on the order. A product bound to the wrong template makes the shipping charge come out differently than you expected.

Preparation time becomes the promise

The preparation time you write per product is the promise you make for handing the order to the carrier. Writing the same time across the whole catalog comes back as a delay on products that take longer to prepare.

Who ships the order can change

An order can ship from your warehouse or from n11, and that split sits on the order. How the stock movement is written to Shopify for an order that does not leave your warehouse is configured separately.

You issue the invoice

n11 asks for the invoice to be attached to the order, but the invoice itself is issued in your e-archive or e-invoice system. Your bookkeeping software is connected to this flow separately.

Return and cancellation requests run in the panel

A return request is opened on the n11 side and works against the seller if it is not closed. Whether the request lands on the Shopify side depends on the tool you use.

An unpaid order is not handed to the carrier

An order whose payment is not confirmed is not shipped, and it should not be marked paid on the Shopify side. If a cancellation arrives you are left with a record that has no counterpart, and shipping and stock movements cannot be tied to that record.

COMMON MISTAKES

The most common mistakes in the Shopify n11 integration

The nine headings below are the mistakes that show up most often in setup. The outcomes look alike as well: the product comes back from review, stock does not hold, or the first order goes out wrong.

Leaving a required attribute empty

A product cannot be sent until the category's required attributes are filled. On categories with a wide tree, this mistake brings dozens of rows back at once in a bulk send.

Giving variants different model codes

When variants of the same product get different model codes, each variant opens its own product page. The customer cannot pick a size, and you end up managing the same product across several pages.

Working from a Trendyol checklist

A barcode is not required on n11; category attributes are. If you arrive with a list prepared for Trendyol, the missing field shows up on the attribute side, not the barcode.

Not defining a shipping template

A product without a delivery template cannot be sent. Fixing the template later means walking the catalog a second time.

Writing the same price to both channels

Sending the Shopify price to n11 as-is does not cover commission. The n11 price is set with a separate rule that includes commission and any shipping share.

Treating VAT as a single value

n11 asks for VAT rate per product. When products on different rates get the same value, the error shows up later on the accounting side.

Not checking the update result

A send-completed message does not mean the product was updated. If the result is not followed, the old quantity stays in the store and overselling starts there.

Looking for the connection password on screen

n11 does not show the password on screen; it sends it to the store's registered email. When you work with a team that cannot reach that inbox, setup stops on the second step.

Forgetting the campaign price on the channel

Opening a discount in Shopify and leaving the n11 price as-is makes you sell the same product at two different amounts. Campaigns have to be written into the channel rule as well.

SCENARIO

Three common problems and how we solve them

The three setup scenarios below show how we handle Shopify n11 integration problems we have solved in stores we connected.

Copying a Trendyol setup onto n11

ProblemThe same setup that already worked for Trendyol was applied to n11. Barcodes were complete so no trouble was expected, but half the catalog never sent. Some of the products that did send opened as separate pages with a single size option.

Causen11 requires the category's required attributes, not a barcode, and those fields were empty. Variants did not share a model code, so each one opened its own product page.

SolutionRequired attributes were filled category by category, and every variant was put on a single model code. A separate checklist was built for each marketplace, and the send was split into category groups.

Writing one value for shipping and preparation time

ProblemThe whole catalog got the same delivery template and the same preparation time. Shipping charges came out higher than expected on small products, and delay notices started on products that take longer to prepare.

Causen11 keeps shipping data on the product's template and preparation time per product. Writing a single value erased both the dimensional-weight difference and the lead-time difference.

SolutionProducts were split into weight and volume groups, and each group was bound to its own template. Products coming from supply got a separate preparation time, and the time promise was updated against stock status.

Treating a product still in review as on sale

ProblemOn setup day the catalog was sent in one pass and a send-completed message was taken as live. Some rows were waiting for seller approval and others sat outside the listing limit; products thought to be unsold for two weeks had never appeared in the store.

Causen11 keeps a product in more than one status, and a product that matches the catalog by barcode moves to waiting for seller approval. The store's listing allowance was also full, so the remaining rows dropped outside the limit.

SolutionProduct statuses were read row by row, and the ones waiting for approval were approved. The catalog was sent in groups, and the next group opened only after each group's result was checked.

STATION

Shopify n11 integration

Station is the tool we built to run the product, stock, price, and order flow from a single panel. When you add Trendyol or Hepsiburada, each channel gets its own rules.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

How do you set up a Shopify n11 integration?

Setup starts once your n11 seller application is approved. After approval you open My Account in Satıcı Ofisi, go to the API Accounts screen, and create a connection account; the key is shown on screen and the password is sent to the store's registered email. You then map categories and required attributes and define your model code, price, stock, and delivery rules. The last step is confirming the flow with a test order placed with a single product.

Is there a ready-made Shopify app for n11?

n11 does not have a Shopify app it built itself. Apps that appear under the n11 name in the App Store belong to third-party developers, and some of them only cover invoicing or stock and never send products to n11. That is why the app's scope has to be checked before setup.

How are Shopify products transferred to n11?

Product transfer starts by binding your Shopify category to n11's lowest-level category. A product cannot be sent until that category's required attributes are filled, so mapping is built category by category. Sent products enter catalog review and appear in the store after they pass.

Is a barcode required on n11?

It is not required. On n11 a product is identified by the category's required attributes and the model code; the barcode is only used to match a record in the n11 catalog. If the barcode you send matches a catalog product, the item moves to waiting for seller approval without looking at attributes.

How do variant products go to n11?

n11 builds variants around the model code: rows that share the same model code appear as options on a single product page. If you do not give every variant of a Shopify product the same model code, each variant opens its own product page and the customer cannot pick a size or color.

How does Shopify n11 inventory sync work?

When a sale happens on one channel, the integration also drops the other channel's quantity. That update does not hit n11 instantly; it first joins a queue, and a message that the system received the request does not mean the product was updated. If the result is not followed, both channels can sell the same product; not showing the last few units on n11 also lowers that risk.

Can the n11 price be managed separately from the Shopify price?

It can, and it should. The n11 price is set with a rule that adds commission and any shipping share on top of the Shopify price; once the rule is defined you do not have to write a price on every product. When you open a campaign, both sides update from the same rule.

How is n11 commission reflected in the price?

The n11 price is set by adding commission and any shipping share on top of the Shopify price. The commission rate changes by category, so you follow the current value in your seller panel. Writing the same price to both channels cuts your margin on n11 sales.

How are n11 orders transferred to Shopify?

The order is placed on n11 and the integration writes it into Shopify as an order record. Warehouse and accounting then work from the same list, and shipping and invoice steps are tied to the Shopify record. Orders whose payment is not confirmed should not be marked paid in Shopify; a cancellation leaves you with a record that has no counterpart.

Where do you get n11 connection credentials?

In Satıcı Ofisi you open My Account, go to the API Accounts screen, and create a new account. Your key is shown on that screen and the password is sent to the store's registered email. That is why you need access to that inbox during setup.

What is a shipping template, and why is it required?

n11 keeps shipping data on a delivery template tied to the product, not on the order, and a product without a template cannot be sent. Splitting products into weight and volume groups and binding each group to its own template keeps the shipping charge from coming out differently than you expected.

What does preparation time do?

How does the integration send the VAT rate?

n11 asks for VAT rate per product, and Shopify does not carry that field. The rate is therefore defined on the integration side; if you have product groups on different VAT rates, the split has to be made during setup.

What do product statuses mean on n11?

n11 keeps a product in separate statuses such as approved, in catalog review, pending, rejected from catalog, outside the limit, and action required. A send-completed message does not guarantee any of those statuses, so the result has to be read row by row on setup day.

Why is my product not being approved?

The three most common reasons are missing required attributes for the category, a category that was not picked at the lowest level, or empty product safety fields. Image resolution and title length can also be grounds for rejection.

What do you need to become an n11 seller?

You need a company, and a sole proprietorship is enough; a store cannot be opened with an individual account. A tax certificate, a signature declaration or circular, an activity certificate, a bank account in the company's name, and a signed seller agreement are the main documents requested. The exact list is on the application screen.

How long does the integration take?

Seller application approval takes a few business days when documents are complete; missing documents stretch that. Building the connection finishes the same day. Products passing catalog review and appearing in the store can take a few days depending on product count and category.

Is the integration paid?

n11 does not charge to open a store and does not ask for a separate fee to use the connection; what you pay is the fee of the integration tool you use. The commission n11 takes on a sale is a separate line from that.

Does the integration issue invoices?

You issue the invoice; n11 asks for it to be attached to the order. Issuing happens in your own e-archive or e-invoice system, and your bookkeeping software is connected to this flow separately.

Can I also connect to Trendyol and Hepsiburada at the same time?

You can, but each marketplace has its own catalog rules and commission rate. n11 does not ask for a barcode while Trendyol does, and Hepsiburada writes the product to the catalog first and to the sale list second. When the same stock is opened to more than one store, stock and price rules have to be set separately for each channel.