Shopify Paraşüt Integration
Every order you sell on Shopify has to become an invoice, a customer account and a stock movement on the pre-accounting side. Writing those three by hand stops being possible as order volume grows. The Shopify Paraşüt integration puts all three on automatic. The e-invoice versus e-archive split follows the buyer's record, tax and shipping charges land on the invoice as separate lines, and which side owns stock is chosen up front.
growing on Shopify with Nodus Works
Shopify Paraşüt integration what is it?
A Shopify Paraşüt integration is the connection that turns a store order into an invoice, a customer account and a stock movement on the pre-accounting side. Because the order is entered once, you do not have to write the same sale into two programs.
Setup starts with your invoice layout being ready in Paraşüt. Then you connect your Shopify store, choose which order status is transferred, define which fields match product and customer cards, and set the tax rules. When product and customer-card matching falls outside the standard fields, Nodus Works' Shopify integration and custom app development service builds that match as a custom setup. The last step is the test invoice you issue from a single order.
Once the connection is live, daily work gets shorter. The order lands in Paraşüt, the invoice is issued by buyer type, the collection is posted to the right account, and you print the shipping slip together with the invoice.
What syncs between Shopify and Paraşüt
Once the connection is live, orders, invoices, customer accounts, product cards, stock and collections become parts of the same flow. The six headings below cover the questions that come up most often in a Shopify Paraşüt integration.
Shopify order transfer
An order created in your store is written into Paraşüt as a sales record. Which order status and which payment status are transferred is decided during setup.
Paraşüt e-invoice and e-archive
The invoice is issued as an e-invoice or an e-archive depending on whether the buyer is a taxpayer. When that split is set up correctly, you do not have to pick the invoice type by hand on every order.
Customer account matching
The customer is tied to a customer account in Paraşüt, so a second order from the same person does not open a new record. Which field the match is built on is set during setup.
Product card and stock movement
The Shopify product is matched to the Paraşüt product card through the stock code. If the invoice should also produce a stock movement, that is set up separately.
Collection and payment record
The order collection is posted to the related customer account so the open balance shows the truth. You can also route different payment methods to different cash or bank accounts.
Return and cancellation invoices
The counterpart of a returned order is a return invoice; a issued invoice is not deleted. Writing this movement into Paraşüt corrects both stock and the account balance.
Bulk invoicing, matching and multi-channel sales
Once you pass a handful of orders a day, issuing invoices one by one is no longer possible. Bulk invoicing, card matching and tying more than one sales channel to the same layout are therefore part of the setup, not extras.
Bulk invoice issuing and printing
You can filter the orders that piled up during the day and invoice them in one pass. Printing the shipping slip and the invoice on a single output removes the need to hunt for two documents at packing.
- Bulk invoicing
- Shipping slip and invoice
- Order filtering
Product and customer account matching
Products match on stock code, customers on tax or identity data. When the matching rule is set correctly from the start, Paraşüt does not open a second record for the same product or the same customer.
- Stock code matching
- Customer account uniqueness
- Automatic card opening
One invoice layout for multi-channel sales
If you also sell on marketplaces besides Shopify, every order can attach to the same invoice layout. The channel split stays on the record; accounting sees a single list.
- Marketplace orders
- Single invoice layout
- Channel-based reporting
How is the Shopify Paraşüt integration done?
The six steps below cover the full setup, from account preparation through the first test invoice. Some steps happen in Paraşüt, some in the Shopify admin; you need an authorized account on both sides.
Prepare the invoice layout in Paraşüt
Connecting before your invoice header, tax details and invoice series layout are ready does not help. If you will issue e-invoices, also confirm that this side of your Paraşüt account is open.
Start the connection from the Paraşüt side
The direction of this setup is the opposite of what most people expect: it does not start by installing an app on Shopify, it starts by adding Shopify as a platform from the ecommerce section of the Paraşüt panel. You can see the scope on parasut.com.
Choose the cash account collections will write to
Setup does not finish without a cash account; order collections write to the account you pick. A cash account that already has a bank connection does not appear in this list; if your virtual payments land in a bank account, you need to plan how reconciliation will work from the start.
Set up product and customer account matching
If a line on the order has not been matched before, the screen asks for a match, and skipping that step makes Paraşüt open a second card for the same product. The same decision is made on the customer side: will every buyer get a separate account, or will retail sales sit under a single account?
Define the tax, shipping and discount rules
A default tax rate is chosen during setup, and that rate applies only when the order does not carry its own rate. Whether your Shopify prices are tax inclusive or exclusive, how the shipping charge appears on the invoice, and which line the discount writes to are also set here.
Verify the invoice with a test order
Issue an invoice from a single order and check that the amount, the tax line and the customer account are correct. Repeating the same test with a corporate buyer also shows that the e-invoice side works.
The table below shows which Shopify fields map to which counterparts in Paraşüt.
| What Shopify has | What it maps to in Paraşüt |
|---|---|
| Order | Sales invoice |
| Customer | Customer account |
| Product and stock code | Product card |
| Order line | Invoice line |
| Shipping charge | Separate line on the invoice |
| Discount and coupon | Line discount or a separate row |
| Payment | Collection record |
| Return | Return invoice |
| Tax identity data | The field that decides the invoice type |
The last row of the table is the most critical part of setup. Whether the buyer is a taxpayer changes the invoice type, so this data has to arrive with the order; if you sell to companies, make sure Shopify is collecting that field.
Tell us about your catalog and current setup, and we will work out how the Shopify Paraşüt 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.
What is the difference between e-invoice and e-archive?
This is the heading where pre-accounting integrations produce the most errors. You do not choose the invoice type; the buyer's identity does. An invoice issued in the wrong type comes back from the other side.
If the buyer is a taxpayer, an e-invoice is issued
When you sell to a tax-registered company, the invoice is issued as an e-invoice and lands in the buyer's system. On this type of invoice the buyer's tax ID has to be correct.
If the buyer is an individual customer, an e-archive is issued
An invoice issued to a customer who is not a company is prepared as an e-archive and sent electronically. Most store sales fall into this group.
The field that decides the type arrives with the order
The integration reads whether the buyer is a taxpayer from the data on the order. If tax data is not collected from a corporate buyer, the invoice is issued in the wrong type and fixing it takes longer than issuing it correctly the first time.
Internet-sale invoices go on a separate series
Invoices issued for sales made over the internet are expected to use a series different from your other invoices. When in-store sales and Shopify orders write to the same series, the layout does not meet the regulation; this split is set at the very start of the invoice layout.
An issued invoice is not edited
Once the invoice is official, you do not correct it in place. You can cancel an e-archive invoice inside a short window; after that window the only path is a return invoice. That is why the test invoice is a setup step you do not skip.
Cancelling an e-invoice is not in your hands
You cannot cancel an invoice issued to a corporate buyer from your own program; cancellation either happens when the buyer rejects the invoice or through the official portal. That is why checking the invoice before you send it matters more in corporate sales.
An invoice for a sale made over the internet must also carry information that an in-store sale does not: the web address where the sale was made, the payment method, the organization that mediated the payment, the payment date, the tax or identity number of the party that carried the goods, the date the goods were sent, a returns section, and a statement that the sale was made over the internet. The paper copy of the invoice going with the shipped goods, and the customer filling in the returns section and sending that copy back with the product if they return it, are part of the same rule. That is why the invoice design also sets your packing flow.
Those fields filling in automatically depends on the integration reading them from the order and carrying them into pre-accounting. A setup that only transfers the amount and the customer name leaves the fields empty, and the gap is usually noticed during an audit. The document Shopify produces at the end of an order is also not a valid invoice in Turkey; the legal document always comes from the pre-accounting side.
Why the invoice total does not match the order
The most common gap comes from the tax rules. If you show prices tax inclusive on Shopify, the same amount has to be split on the pre-accounting side into a tax-exclusive amount and a tax line. When that split rule is wrong, every invoice picks up a small but constant fractional difference, and at month end you get a report that does not tie.
The default tax rate you pick during setup is also misunderstood. That rate is not a rule applied to every invoice; it is a fallback that only kicks in when the order does not carry its own rate. If your catalog has products at different rates, the rate has to be defined on Shopify at product or collection level; a setup that trusts a single fixed rate produces wrong invoices on a mixed catalog.
The second cause is the shipping charge and discounts. The shipping charge stands as a separate line on the invoice and has its own tax rate. The discount appears either on the line or as a separate row; when both are used on the same order, how the amount is calculated has to be decided from the start.
The third cause is currency. If you sell in a foreign currency, the rate used to issue the invoice is written on the record, and the exchange difference between the sale date and the collection date is tracked as a separate line. Setups that skip this split never get the customer-account balance back to zero.
Which side owns stock?
This question is answered before setup. Both Shopify and Paraşüt can hold stock, and when both write independently the counts drift over time; fixing the drift later means taking a physical count.
One system of record is chosen
You decide which program holds the real stock count; the other follows it. Paraşüt's ecommerce package is designed to treat its own side as the source and write to the store; if your warehouse runs from Shopify, whether that direction fits your workflow is discussed before setup.
An invoice does not always produce a stock movement
In a setup that only issues invoices, the stock card in Paraşüt never moves. Invoice apps in the App Store fall into this group; if you also want stock, you need a wider setup.
Warehouse splits are carried into pre-accounting
If you sell from more than one Shopify location, that split needs a counterpart on the pre-accounting side. In a setup that writes every warehouse onto a single card, you cannot see what left which warehouse.
A return puts stock back
A returned product goes back into sellable stock, and that movement has to be written on both sides. If you only issue a return invoice and do not write the stock movement, the count stays short.
An unmatched product opens a new card
If a line on the order has not been matched before, Paraşüt opens a second card for the same product. Once a few cards pile up for the same product, neither the stock report nor the profit report is readable, so matching is not skipped.
Variants are grouped under one parent product
Variants from different channels are tied to a single parent product in Paraşüt, and total stock is tracked under that parent. If you want stock tracked per variant, you need to confirm which package includes that before setup.
When the pre-accounting connection is set up on its own, the stock question stays between Shopify and Paraşüt. If you also sell on marketplaces, the same stock is opened to three or four places and the question grows: the stock rule on Trendyol, Hepsiburada and n11 runs separately, so look at Station to manage product, stock, orders and invoices from a single panel.
What happens after the order arrives?
The order is created on Shopify and the integration writes it into Paraşüt. What follows is invoicing, collection, shipping and returns; the order of those steps changes with the settings you pick during setup.
Order status decides when the transfer happens
The order is written into Paraşüt when it reaches the status you chose. Picking that status too early invoices sales that are not yet confirmed; picking it too late leaves a list that piles up at the end of the day.
Collections write to the cash account you chose
Order collections post to the single cash account you picked during setup, and cash accounts with a bank connection do not appear in that list. If your virtual payments land directly in a bank account, you need to decide from the start how the two records will be compared.
The shipping slip may not carry a barcode
If no carrier contract is attached, the slip that is produced only carries address and order data; you take the barcode from the carrier's own panel. As daily parcel counts grow, the back and forth between those two screens becomes the real slowdown.
Cancellation and returns are separate jobs
Cancelling an order that has not been invoiced only closes the record; an order that has been invoiced needs a return invoice. Tying both to the same flow breaks the account balance.
If address data arrives incomplete, the invoice is not issued
An address is required on the invoice, so when an order lands on the pre-accounting side without an address that row cannot be invoiced and waits in the list. The cause is usually not the setup but your store plan not sharing address data; it is checked before setup.
No record is opened after the accounting period closes
An order that lands close to midnight at month end can sit in the transfer queue while the period closes, and pre-accounting then refuses the record. For those records not to disappear silently, the transfer has to raise an alert when it errors; looking at the waiting list at month-end close also has to become a routine.
The most common mistakes in the Shopify Paraşüt integration
The nine headings below are the mistakes that come up most often in setup. The results look alike too: the invoice total does not match, customer accounts swell, or stock does not show the truth.
Not checking the tax rules
When whether Shopify prices are tax inclusive or exclusive is set wrongly on the pre-accounting side, every invoice picks up a small difference. The gap is invisible on a single sale and shows up in the month-end total.
Not collecting tax data from corporate buyers
A corporate sale without a tax ID is invoiced in the wrong type. When the buyer does not accept the invoice, you have to cancel and reissue.
Opening a new customer account on every order
When account matching is not set up, the same customer piles up as dozens of records. Neither the open balance nor the customer history stays readable.
Not writing the shipping charge onto the invoice
When the shipping charge collected from the customer does not appear on the invoice, the invoice total stays below the order total. The collection then does not close the invoice either.
Writing stock on both sides
When Shopify and Paraşüt write the same product's stock independently, the counts drift. The only way to fix the drift is a physical count.
Invoicing an order whose payment is not complete
When an invoice is issued for an uncollected sale and the order is then cancelled, you are left with an invoice that has no counterpart. Closing that record requires a return invoice.
Trying to fix a return by deleting the invoice
An issued invoice is not deleted; it is corrected with a return invoice. Trying to delete it breaks the number sequence and leaves a gap you later have to explain.
Skipping the test invoice
Whether the setup is correct only shows on a real invoice. In setups that go live without a test, the error comes out on the first busy day and in bulk.
Thinking about the discount line later
When how coupons and discounts appear on the invoice is not set from the start, invoices for the same campaign come out in different shapes. The discount amount cannot be totaled in reports.
Three common problems and how they were solved
The three setup scenarios below show how we handled Shopify Paraşüt integration problems we solved in stores we connected.
A sales report that did not tie at month end
ProblemInvoices were being issued cleanly, but at month end the sales total in pre-accounting came in below the store report. The gap was small on every invoice, so it went unnoticed for weeks.
CauseThe store showed prices tax inclusive, while the pre-accounting side treated the amount as tax exclusive and added tax on top. The shipping charge was also never written onto the invoice.
SolutionThe tax rules were rebuilt to match how the store displays prices, and the shipping charge became a separate invoice line. A difference list was produced for the past period and closed with correction invoices.
Dozens of records for the same customer
ProblemAfter a year, thousands of customer accounts had piled up in pre-accounting and every order from regular customers had opened a separate record. The open-balance report became unusable.
CauseAccount matching had not been set up, so every order opened a new card. Tax data was also not collected from corporate buyers, so some of them had been invoiced in the wrong type.
SolutionThe matching rule was built on identity and tax data, and duplicate cards were merged. A tax ID field was opened on the store for corporate buyers, and the invoice type started being decided from that field.
Stock drifting between the two programs
ProblemStore and pre-accounting counts moved apart over the months. Marketplace sales were also tied to the same stock, so it became unclear which number was correct.
CauseBoth programs were writing stock, and which one was the system of record had never been decided. On returns, only an invoice was issued and no stock movement was written.
SolutionThe store was fixed as the system of record for stock, and pre-accounting was set to follow it. A stock movement was added to the return flow, a physical count was taken once, and both sides were started from the same point.
Station is the tool we built to run the order, invoice, account and stock flow from a single panel. When marketplaces such as Trendyol or Hepsiburada are added, every channel's orders attach to the same invoice layout.
Frequently Asked Questions
How is the Shopify Paraşüt integration done?
Does Paraşüt have an official Shopify app?
What is the difference between e-invoice and e-archive?
How is the invoice type decided?
Is a separate series required for internet-sale invoices?
Which information must appear on an internet-sale invoice?
Is the invoice Shopify issues enough?
Can an issued invoice be corrected?
Are Shopify orders transferred to Paraşüt automatically?
What happens to orders whose payment is not complete?
Why does the invoice total not match the order total?
How does the shipping charge appear on the invoice?
How do discounts and coupons land on the invoice?
Should stock be held in Shopify or in Paraşüt?
Does stock also drop when an invoice is issued?
How are products matched?
Can a single customer account be kept for the same customer?
How are returns processed?
Shopify orders are not transferring to Paraşüt. What should be checked?
Can orders that arrive at month end be written into a closed period?
Can marketplace orders also be transferred to Paraşüt?
Can invoices be issued in bulk?
How long does the integration take?
Is the integration paid?
How are invoices issued on international sales?
BİZİ TERCİH
EDENLERİN ARASINDA
YER ALIN...
Herkes için Shopify çözümleri üretiyoruz.
Yeni bir Shopify mağazası kurmak, mevcut mağazanızı geliştirmek, özel entegrasyonlar yapmak veya hız problemlerini çözmek mi istiyorsunuz? Biz, teknik işleri sizin yerinize çözen uzman bir Shopify partneriyiz.

Dossha
#shopify

Les Benjamins
#shopify

Nocturne
#shopify

Fellas
#shopify

Mai
#shopify

Karaca
#shopify

Milagron
#shopify

Kiğılı
#shopifySeo

Şölen
#shopify

Adell
#shopifyB2B

Ohora
#shopify

Rendrea
#shopifyBooking

Babeskin
#shopify

The New Lab
#shopify

DTF Town
#shopify

Eczaclick
#shopifySeo

Termos Dünyası
#shopify

Halı.net
#shopify

Blend-r
#shopify

Oioi
#shopifySeo

Nowshopfun
#shopify

Marie Claire
#shopify

Gaziburma
#shopify

Dünyada Kitap
#shopify
NEDEN BİZİMLE
ÇALIŞMANIZ GEREKTİĞİNİ
SİZE ANLATMAK İSTERİZ
Shopify'ı çok iyi anlıyoruz; Türkiye'de her segmentin karşısına biz olarak çıkıyoruz :)







Sadece Shopify konuşanlardan oluşan bir takım

Hey!
Bannerlarım kesik gözüküyor :(
Yardım eder misiniz, kampanya dönemindeyim.
Selam Elif!
2 dakikaya çözüyoruz.





.webp)
.webp)


