Shopify Pazarama Integration

To sell your Shopify products on Pazarama, the two systems have to keep talking to each other. Pazarama 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 the channel's barcode, group-code, and approval rules cut into that flow. We also do not hide what the channel does not publish; we wrote separately which details you need to confirm in your panel.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Pazarama integration what is it?

A Shopify Pazarama integration is the connection that keeps your products, stock quantities, prices, and incoming orders aligned in both systems. Because Pazarama 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 Pazarama seller application is approved. After approval you take your integration credentials from the account information section of the panel, map categories, build your barcode and group-code setup, and define your price and stock rules. When the barcode and group-code setup falls outside 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 Pazarama land in Shopify, stock drops on both sides when a product sells, and you manage prices through a rule instead of rewriting them product by product. You also have to account for product updates going into review as well.

WHAT SYNCS

What syncs between Shopify and Pazarama

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 Pazarama integration.

Pazarama product transfer and sync

Your Shopify products are sent to Pazarama after category mapping is in place. A sent product enters an approval process, so finishing the transfer is not the same as going live; updates you make later go through the same review.

Shopify Pazarama 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 the channel.

Shopify Pazarama price sync

The Pazarama 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.

Pazarama order transfer

Orders placed on Pazarama 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.

Pazarama shipping and dispatch details

Dispatch time and the dispatch and return address are defined at product level, and the carrier can also be picked per product. Which panel you work from for labels and tracking numbers is decided during setup.

Pazarama invoice flow

You issue the invoice in your own e-archive or e-invoice system. The channel's return rule asks for the product to come back with its invoice, so putting the invoice in the parcel is the arrangement that is expected in practice.

CATALOG

Where do Pazarama catalog rules diverge from Trendyol?

If you arrive at Pazarama with habits built on Trendyol or Hepsiburada, the barcode and variant side is the first place that surprises you. The fields that identify a product and how approval works are different on this channel.

A barcode is required, but an international code is not

Pazarama asks for a barcode on every product, but it does not have to be an international barcode; if your product has none, a unique code of enough length is generated. Hepsiburada requires a specific barcode format, so you cannot run the two channels from the same checklist.

The barcode is not changed after upload

The product's link to its channel record is built on the barcode. Changing the barcode after the upload finishes breaks the match and opens the same product as a second record.

The group code defines the variant

Records that share the same group code merge under a single product, and color and size are mapped from the variant table under that code. If the group code is not assigned consistently, each variant is listed as a separate product and the customer cannot pick a size.

An updated product also goes into review

Approval is not a step that happens only on the first upload; when you change a live product the record can fall back into waiting-for-approval. That is why staying on the price and stock side during campaign days is safer than changing content.

Required fields sit in a single list

Product name, barcode, category, brand, description, image, price, tax rate, and stock quantity are among the required fields. On the channel's own upload template, required headings are marked in a separate color, so you can see a missing field on the template itself.

Dispatch information is a field on the product

Dispatch time and the dispatch and return address are defined at product level. Writing the same time across the whole catalog comes back as a delay on products coming from supply; if you have more than one warehouse, the return address pointing at the right warehouse also matters.

This channel has no published rejection-code table. Sources list missing or wrong barcodes, the wrong category, empty required fields, and image problems, but there is no official list that shows which reason comes back under which code. That is why sending the catalog in groups instead of all at once is the fastest way to see the rejection reason on your own list.

SETUP

How do you set up a Shopify Pazarama integration?

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

Open your Pazarama seller account

The application is submitted from the partner screen at isortagim.pazarama.com. After the pre-application form comes verification; you set your password and upload your documents to the panel's document management area.

Upload the seller agreement signed

The channel asks for a stamped and signed copy of the partnership agreement to be uploaded to the panel, and it gives a set window for that after store approval. Sellers who approve through registered electronic mail are exempt from this step.

Collect your integration credentials

From the store name at the top right of the panel you go to account information, then to the integration credentials tab; your seller identity and connection keys sit on that screen. On most sellers these details are visible directly; if they are not, you need to open an access request through support.

Build the barcode and group-code setup

You decide the rule for generating a unique code on products without a barcode, and you give every variant of the same product the same group code. Those two decisions are the most critical part of setup; changing the barcode after upload breaks the match, so fixing it later is expensive.

Define the price, stock, and dispatch rule

Instead of sending the Shopify price as-is, set a channel price that includes commission. Dispatch time and the dispatch and return address are asked for per product, so those field values also 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 Pazarama fields your Shopify fields map to, using the names you see in the panel.

What you have in Shopify	What it maps to on Pazarama
Title	Product name
SKU	Seller stock code
Barcode	Barcode, the axis of the match, not changed later
Product group	Group code, keeps variants under a single product
Variant	Color and size, mapped from the variant table
Price	Sale price
Inventory	Sellable quantity
Brand	Required field
Image	Product images
No Shopify field	Tax rate, dispatch time, dispatch and return address

The last row is the part of setup that is missed most often. Tax rate, dispatch time, and the dispatch and return address are details the channel asks for that Shopify does not carry; those field values are defined 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 Pazarama 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 a Pazarama seller?

To sell on Pazarama 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. The channel says it does not charge to open a store; payment runs as commission when a sale happens.

Company and tax documents

A current tax certificate, a signature declaration or circular, and an activity certificate sit at the top of the list. Legal entities also add the trade registry gazette; those registered in the trade registry also add a central registry record.

A signed partnership agreement

The agreement template is downloaded from the panel and uploaded back stamped and signed; the store does not fully open until this step is done. A separate path is defined for sellers who approve through registered electronic mail.

A bank account in the company's name

The account that sales proceeds go into is asked to be in the company's name; a personal account is not accepted. Structures such as a simple partnership or an association are asked for extra documents such as a partnership agreement or a charter.

The current document list is always on the application screen at isortagim.pazarama.com. Seller approval, integration credentials becoming visible, 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	The channel does not publish an official timeline	We do not give a single day because the timelines in sources contradict each other
Uploading the signed agreement	Within a set window after approval	The store does not fully open if it is not uploaded
Collecting integration credentials	Same day	A request is opened through support if they are not visible in the panel
Products going live	Depends on the approval process	Every product goes through review, and updates also go into review
Steady sales	The first weeks	Price, dispatch time, and return performance start to matter here

PRICING

How does Pazarama commission show up in the price?

Pazarama commission runs by category, but the channel does not publish a public rate list. The only value that binds you is the rate sitting in the agreements area of your panel. Tables circulating on the internet contradict each other, and none of them has the channel itself as a source.

When you read your agreement, look at two more things besides commission: whether the rate is calculated on an amount including or excluding tax, and whether there is a separate per-shipment service fee. Those two lines do not agree across third-party sources, and they change your margin math directly.

One standout line on the channel is that commission is stated as not applied in handmade and women-producer categories. That is a practice with no counterpart on Trendyol or Hepsiburada; if you have products in those categories it is worth checking how it is defined in your agreement.

If you send the Shopify price to Pazarama 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.

CONFIRM IN YOUR PANEL

What do you need to confirm in your panel on this channel?

Pazarama does not publish publicly some of the information the large marketplaces publish. Knowing that is not a disadvantage; it is how you plan setup correctly: you will confirm the six headings below in your own panel, not on the internet.

Your commission rate

Category-based rates do not sit on a public page. The value that counts for you is in the agreements area of your panel; outside tables inform, they do not commit.

A per-shipment service fee

Whether a fee is taken per order or per shipment besides commission contradicts across sources. Checking whether that line exists in your agreement affects margin directly on low-value products.

How long a stock update takes to land

The channel does not publish a landing time; the times on the internet are integration tools' own working periods. Measuring the real time from your own records after setup is the soundest approach.

Which carriers you will work with

A published contracted-carrier list could not be found, yet a carrier can be picked per product. Clarify before setup which firms are defined on your account and which panel you print the label from.

Product rejection reasons

There is no published rejection-code table. Sending the catalog in groups is the fastest way to see which reason shows up on which product on your own list.

How rule changes are announced

The channel has no public changelog. Following the announcements of the tool you connected with is better than noticing a rule change when orders stall.

STOCK

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

A stock change does not hit the channel 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. Because the channel has no published landing time, you have to measure the real time from your own records.

Two channels sell from the same stock

If Shopify and Pazarama 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 performance.

Writing stock on a product still in review

A product that has not finished approval does not appear in the store, so stock written on it does nothing. You also have to account for updates going into review; a product you think is live may be waiting in review because of a change.

Writing stock from a multi-location Shopify setup

Sending the sum of every location makes unsellable units appear on the channel. Because dispatch and return address are defined per product, which warehouse is tied to which product also matters.

Cancellations and returns restore stock

A cancelled or returned product goes back into sellable stock. If that movement is not written to Shopify, the two quantities drift apart over time and the only way to fix it is a count.

Hiding the last few units from the store

Not showing the last few units on the channel 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 performance. 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 Pazarama as a second or third channel next to the large ones, 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 Pazarama and the integration writes it into Shopify. From there the work is packing, shipping, invoicing, and returns. The return side is the clearest rule the channel publishes itself, so that is where you start.

The return calendar is fixed

After the buyer opens a return request they hand the product to the carrier within seven business days, and you are asked to respond to the request within four business days after the product reaches you. Requests not answered inside that window work against you, so the return screen has to sit on the daily follow-up list.

The return comes back with the product's invoice

The channel's return rule asks for the product to be sent with its box, accessories, and invoice. When you set up an arrangement that does not put the invoice in the parcel, return assessment gets harder.

Return shipping is free for the buyer

The buyer sends the return without paying a charge. On an order taken under a free-shipping campaign you also have to account for the outbound shipping charge being deducted from the refund amount after the return.

The carrier can be picked per product

A published contracted-carrier list could not be found, yet a carrier can be defined at product level. Whether you print the label from the channel panel or from your own tool is settled during setup.

Dispatch time becomes the promise

The dispatch 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.

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 Pazarama integration

The nine headings below are the mistakes that show up most often in setup. The outcomes look alike as well: the product never goes live, variants scatter, or the margin comes out lower than expected.

Changing the barcode after upload

The product's link to its channel record is built on the barcode. Changing the barcode breaks the match and the same product opens as a second record.

Giving variants different group codes

When variants of the same product get different group codes, each variant is listed as a separate product. The customer cannot pick a size, and you end up managing the same product across several records.

Working from a Hepsiburada checklist

Pazarama does not require an international barcode format; a unique code can be generated for a product without one. If you arrive with a list prepared for Hepsiburada, you walk into an unnecessary barcode-buying job.

Not knowing that updates go into review

Changing content on a live product can drop the record back into review. Changing the title or description on a campaign day takes the product off the store temporarily.

Setting the price from a commission table on the internet

The channel does not publish a public rate list, and the tables in circulation contradict each other. The price rule is built against the rate in the agreement in your panel.

Not accounting for a service fee

If there is a per-shipment fee besides commission, margin erodes on low-value products. Setting a price without checking whether that line exists in the agreement comes back later as a loss.

Writing a single value for dispatch time

The channel asks for this time per product. Writing the same time across the whole catalog leads to delay notices on products coming from supply.

Not following the return screen daily

Not answering a request inside the window works against you. When the return screen is not on the daily list, the loss can be larger than the product itself.

Not putting the invoice in the parcel

The return rule asks for the product to come back with its invoice. A parcel that left without an invoice makes return assessment and the conversation with the customer harder.

SCENARIO

Three common problems and how we solve them

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

Variants being listed as separate products

ProblemThe catalog was sent to the channel and the products went live, but every size of the same model sat on its own page. Customers could not pick a size, so pages left with a single size did not sell, and the store had to manage the catalog as several hundred records.

CauseThe channel builds the variant with a group code, and during the send each variant had taken its own code. Variant structure is built differently on Trendyol, so the same file was assumed to work here as well.

SolutionEvery variant was put on a single group code, and color and size were mapped from the variant table. A resend was done with barcodes kept, duplicate records were closed, and a separate checklist was built for each marketplace.

Profit falling while sales rose

ProblemOrder volume was above expectation, yet profit at month end came in below it. Prices had been set from a commission table on the internet and no error was visible.

CauseThe rate in the agreement sitting in the panel was different from the table the price rule was built on. A per-order fee besides commission was added on top; on low-value products a sale had turned into a loss.

SolutionThe price rule was rebuilt against the real rate in the agreement, and the per-shipment fee was added to the rule as well. Low-value products were treated as a separate group, and some of them were turned into packs.

A product thought to be live waiting in review

ProblemWeeks after setup a price update was made, and then those products stopped getting orders. The products were still in the panel and stock was written; the problem was thought to be a drop in demand.

CauseThe channel takes updates into review, not only the first upload. The content change had dropped the records back into waiting-for-approval, and the products had not appeared in the store during that stretch.

SolutionUpdates were split into groups and moved to quieter days, and on campaign days only the price and stock side was touched. Product statuses were bound to a regularly read list, and records waiting in review became something that could be followed.

STATION

Shopify Pazarama 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 Pazarama integration?

Setup starts with your Pazarama seller application being approved and the signed partnership agreement being uploaded to the panel. From the store name at the top right of the panel you then go to account information, then to the integration credentials tab, and take your seller identity and connection keys. The next steps are category mapping, barcode and group-code setup, the price and stock rule, and defining dispatch information per product. The last step is confirming the flow with a test order placed with a single product.

Is there a ready-made Shopify app for Pazarama?

Pazarama does not have a Shopify app it publishes itself. The connection is built with an integration tool that supports Shopify and Pazarama together; most of those tools are not Shopify apps, they are a separate panel that sits between the two. Their scope is not one-size-fits-all either, so before setup you have to check what they cover on the product, stock, order, and invoice side.

Where do you get Pazarama integration credentials?

After you enter the panel you go from the store name at the top right to account information, then to the integration credentials tab; your seller identity and connection keys sit on that screen. On most sellers the details are visible directly; if they are not, an access request has to be opened through support. That is why it is good to leave a day of slack for this step in the setup plan.

Is a company required to sell on Pazarama?

It is. You need a tax number as a sole proprietorship, a limited company, or a joint-stock company; 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 partnership agreement are the main documents requested; the exact list is on the application screen.

How many days does the seller application take to be approved?

The channel does not publish an official approval time, and the times on the internet contradict each other. What usually sets the timeline is documents being complete and the signed agreement being uploaded on time. The store does not fully open if the agreement is not uploaded.

Is a barcode required on Pazarama?

A barcode is among the required fields, but it does not have to be an international barcode; if your product has none, a unique code of enough length can be generated. That is the opposite of Hepsiburada, which requires a specific barcode format. The match is built on the barcode, though, so the barcode must not be changed after the upload finishes.

What happens if I change the barcode?

The product's link to its channel record breaks, and the same product can open as a second record. In that case stock and price updates go to the wrong record, and the same product appears twice in the store. Getting the barcode setup right once during setup is much easier than fixing it later.

How do variant products go to Pazarama?

The group code defines the variant: records that share the same group code merge under a single product, and color and size are mapped from the variant table under that code. When the group code is not assigned consistently, each variant is listed as a separate product and the customer cannot pick a size. The attribute split that opens a separate product card on Trendyol does not exist on this channel.

How are Shopify products transferred to Pazarama?

Product transfer starts by binding your Shopify category to a Pazarama category, and a product cannot be sent until the required fields are filled. A sent product does not go live directly; it falls into waiting-for-approval and goes through review. That is why finishing the transfer is not the same as going live.

Why is my product waiting for approval?

The channel takes every uploaded product into review, and that can be a matter of a business day. The important detail: approval can also kick in when you change a live product, not only on the first upload. A product you think is live may be waiting in review because of an update you made.

Why was my product rejected?

There is no published rejection-code table, so the reason cannot be read from a definitive list. The reasons that come up most in sources are a missing or wrong barcode, the wrong category, an empty required field, and image problems. Sending the catalog in groups is the fastest way to see which reason shows up on which product.

What are Pazarama commission rates?

Commission runs by category, but the channel does not publish a public rate list. Tables circulating on the internet contradict each other, and none of them has the channel itself as a source; the only value that binds you is the rate sitting in the agreements in your panel. When you read the agreement you also have to look at whether the rate is calculated on an amount including or excluding tax.

Is there a deduction besides commission?

Whether a separate per-shipment or per-order service fee is taken does not agree across third-party sources, so you can only confirm this from your own agreement. If you sell low-value products this line can affect margin more than commission, so it has to be checked before the price rule is set.

Is commission not taken in handmade and producer categories?

One of the channel's standout practices is that commission is stated as not applied in handmade and women-producer categories. That is a line with no counterpart on Trendyol or Hepsiburada. If you have products in those categories it is worth checking how it is defined in your agreement, because what binds you is still your agreement.

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

It can, and it should. The channel price is set with a rule that adds commission, any service fee, and a 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 does Shopify Pazarama inventory sync work?

When a sale happens on one channel, the integration also drops the other channel's quantity. That update does not land instantly; it first joins a queue, and a send-completed message does not mean the product was updated. The channel does not give a published landing time, so the real time has to be measured from your own records after setup.

How are Pazarama orders transferred to Shopify?

The order is placed on Pazarama 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.

Which carrier is used?

A published contracted-carrier list could not be found, yet a carrier can be defined at product level. So there is no structure locked to a single firm. Which firms are defined on your account, and whether you print the label from the channel panel or from your own tool, has to be settled before setup.

What does dispatch time do?

The dispatch time you write per product is the promise you make for handing the order to the carrier. The dispatch and return address are also defined at product level the same way. Writing the same time across the whole catalog comes back as a delay on products coming from supply.

How do returns work on Pazarama?

After the buyer opens a return request they hand the product to the carrier within seven business days, and you are asked to respond to the request within four business days after the product reaches you. The refund starts after approval. Requests not answered inside the window work against you, so the return screen has to sit on the daily follow-up list.

Who pays return shipping?

The return shipment is free for the buyer. On an order taken under a free-shipping campaign you also have to account for the outbound shipping charge being deducted from the refund amount after the return. The product is asked to come back with its box, accessories, and invoice.

Does the integration issue the invoice?

You issue the invoice; issuing happens in your own e-archive or e-invoice system, and your bookkeeping software is connected to this flow separately. The channel's return rule asks for the product to come back with its invoice, so putting the invoice in the parcel is the arrangement that is expected in practice.

How long does the integration take?

Building the connection finishes the same day. Two things set the timeline: seller application approval and integration credentials becoming visible in the panel. The channel does not publish a time for approval, and a support request is needed when the credentials are not visible, so those two steps have to be put at the front of setup.

Can I use Pazarama as my main channel?

The channel runs at a smaller scale than the large marketplaces and does not publish commission, service fee, or stock landing time publicly. For those two reasons it is not the main channel for most sellers; it makes sense as a second or third channel next to Trendyol and Hepsiburada. When you open the same stock to more than one channel, the rules have to be set separately for each one.

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. Pazarama does not require an international barcode while Hepsiburada asks for a specific format, and Trendyol builds the variant with a different mechanism. When the same stock is opened to more than one store, stock and price rules have to be set separately for each channel.