From Shopify sale to Sellsy back office
Let Shopify capture the sale while Sellsy carries the financial and operational record behind it. Synchron can turn eligible Shopify orders into Sellsy invoices, translate Shopify refunds into credit notes, connect customer and document context across both systems, and let Sellsy inventory drive the stock shown in Shopify.
One commercial event, one connected back-office trail
An ecommerce sale does not end when Shopify marks the order as paid. Finance may still need a customer record, an invoice, a payment entry or delivery paperwork; a later refund may require a credit note; and stock may be controlled by the back office rather than the storefront. Synchron connects those responsibilities so Shopify and Sellsy can each remain authoritative for the work they are best placed to manage.
Shopify Plus teams can use the proven Shopify workflow model behind this connection.
Available workflows
Synchron turns Shopify sales and refunds into the Sellsy documents your back office works with, while inventory can travel the other way when Sellsy owns the stock position.
Turn eligible Shopify orders into Sellsy invoices with customer details, product lines, prices, taxes and shipping information. Keep invoice validation, payment recording and additional Sellsy documents as separate choices within the same sales process.
Create Sellsy credit notes from full or partial Shopify refunds, matching the original customer, products and invoice where possible. Finance can review draft credit notes, with optional document links back to the Shopify order.
Use Sellsy stock movements to update inventory at the configured Shopify location on an hourly schedule. Give stock one operational owner and reduce manual quantity updates in the storefront.
How it works
The connection follows the commercial events that matter after a customer buys: the original sale, the documents finance needs, any later refund and the inventory position behind future orders.
Shopify remains the source for the ecommerce order, with the customer, products, shipping, pricing and payment context captured during checkout.
Synchron uses that commerce context to build the corresponding Sellsy invoice and customer relationship so the back office does not have to re-enter the sale.
Invoice validation, payment recording, delivery paperwork and related Sellsy processes can follow the level of automation your team is comfortable with.
If Shopify records a refund, Sellsy can receive the related credit note; if Sellsy owns inventory, its stock movements can update the availability presented in Shopify.
Monitoring active visibility
Invoices and credit notes are business records, so a failed hand-off matters differently from a cosmetic website update. Synchron keeps the movement between Shopify and Sellsy visible so teams can understand whether a sale, refund or stock change reached the system that owns the next step.
See the operational trail behind the Shopify sale becoming a Sellsy financial document rather than assuming the back-office record exists.
Understand whether a Shopify refund produced the corresponding Sellsy credit-note activity before finance closes the period or customer service considers the case finished.
When a Sellsy stock movement does not produce the Shopify availability you expect, your team has a clearer place to review the integration activity behind it.
Why Synchron.io
Shopify is built to make selling easy. Sellsy gives finance and operations a structured place for documents, customer records and stock. Synchron lets each system keep that role while removing the repetitive hand-offs between them.
Carry the order context already captured in Shopify into Sellsy instead of asking finance to reconstruct the sale from scratch.
Connect Shopify refund activity to Sellsy credit notes so after-sales decisions do not stop at the storefront.
Choose how much of the document lifecycle should be automated while keeping review and validation where your internal controls require them.
Let Sellsy drive Shopify availability when inventory is managed by the warehouse or back-office team rather than by the ecommerce storefront.
Use operational monitoring to understand what moved successfully and what still needs attention across orders, refunds and inventory.
Useful invoice automation starts with a sale your finance team can recognize. Decide which orders should enter Sellsy and how their customers, products and shipping charges should be represented.
The default import selects paid, open Shopify orders, regardless of fulfillment status. Payment, order, fulfillment and currency filters let your team align invoicing with its own sales process rather than treating every order identically.
The order flow can match or create Sellsy customers using Shopify billing and shipping details. Adding a shipping address to the Sellsy customer is a separate option, useful when the back office also prepares delivery documents.
Consistent SKUs help Shopify and Sellsy identify the same products. Shipping methods also need the correct Sellsy item or service mapping, including when a refund covers shipping costs.
The import reuses Shopify line quantities, prices, taxes and shipping data. Tax-exclusive amounts and rounding adjustments are configurable, so finance should check representative document totals before changing how amounts are handled.
The three flows run on different schedules. Finance, customer service and warehouse teams can plan invoice reviews, refund checks and stock updates around the next scheduled run.
The order flow checks the previous 3 hours for eligible Shopify orders and creates Sellsy invoices. Manual import lets your team test selected orders, backfill older sales or reprocess an order after correcting an issue.
The refund flow checks the previous 2 hours of refunded or partially refunded Shopify orders. Manual import helps review a specific refund or reconcile historical refunds without relying only on the scheduled window.
The inventory flow checks the previous hour of Sellsy stock movements and updates the configured Shopify location. Stock changes can therefore take time to appear in the storefront; this flow is distinct from order and refund imports.
The same three flows can serve different teams without asking everyone to work in the same tool. Choose the document controls and stock ownership that fit your daily operation.
A merchant receiving paid Shopify orders can prepare Sellsy invoices for review, then enable automatic validation or payment recording when those steps fit the process. Finance spends less time re-entering sales while retaining its checkpoints.
Customer service handles the refund in Shopify, while finance reviews the corresponding Sellsy credit note. Optional links on the Shopify order help support find the financial document without another hand-off to the back office.
When the warehouse manages receipts and corrections in Sellsy, the hourly inventory flow updates the chosen Shopify location. Teams avoid maintaining the same quantity independently in two systems while allowing for the scheduled update interval.
The right automation is not always “create and finalise everything immediately.” Different finance teams want different checkpoints. Synchron can move the Shopify order into Sellsy while preserving the review, validation and payment process that fits your accounting operation.
Keep newly created documents in a state your finance team can inspect before they become part of the final invoicing process.
For predictable ecommerce sales, the workflow can go further and reduce the manual step between creating a Sellsy invoice and treating it as an approved document.
When your financial process calls for it, a paid ecommerce order can also feed the corresponding payment record in Sellsy rather than leaving the invoice apparently unpaid.
Where your warehouse or administrative process relies on Sellsy delivery or order documents, those can sit around the same order-to-invoice flow instead of requiring another data-entry routine.
Refunds are where ecommerce and finance records often drift apart. Customer service may complete the refund in Shopify, but the back office still needs a document trail that reflects the reduction in the original sale.
Where the Shopify order has already become a Sellsy invoice, the refund workflow can connect the financial correction back to that existing customer and sales record.
A refund does not have to reverse the entire order. Sellsy credit notes can reflect the portion of the Shopify sale that was actually refunded.
Credit-note creation can support a review-first process rather than forcing every ecommerce refund directly into a final accounting document.
Moving financial documents into Sellsy should not make them disappear from the people still working in Shopify. Where useful, the connection can leave a route back to the Sellsy document so customer-service and operations teams can find the financial record without searching another system from scratch.
Give teams working from Shopify a clearer path to the Sellsy invoice created from that ecommerce order.
When a refund creates a Sellsy credit note, the relationship can remain discoverable from the order context used by customer-service teams.
Support, operations and finance can work in the system that suits their role while still being able to follow the same commercial event across both platforms.
Not every Shopify merchant wants the storefront to be the inventory authority. When goods receipts, reservations, adjustments and warehouse corrections are managed in Sellsy, the stock direction can be reversed so Shopify follows the operational quantity instead.
Use Sellsy as the stock master when that is where your operations team actually manages product availability.
Stock received, sold, reserved or corrected in Sellsy can influence the quantity Shopify presents to customers.
A clear source-of-truth model reduces the confusion created when finance, warehouse and ecommerce teams independently maintain different quantities for the same products.
Integration FAQs
Shopify Plus keeps its own public identity here, while the connected workflows follow the verified Shopify integration model described on this page.
Your Sellsy document workflow has extra steps?
Tell us when your team validates invoices, records payments, creates delivery documents and updates stock. We can discuss how Shopify should feed that process without taking control away from finance.
Yes. Synchron can turn eligible Shopify orders into Sellsy invoices using the customer, product, pricing, tax and shipping context captured by the ecommerce sale.
No. Automatic invoice validation is disabled by default, so finance can review drafts before validation. Enable that step when it matches your review process; payment recording and additional Sellsy documents are separate options.
Yes. Optional steps can record a payment in Sellsy for a sale already paid in Shopify, create delivery documents and create a separate Sellsy order document alongside the invoice. Choose each step to fit how finance and operations handle the sale.
Yes. Full and partial Shopify refunds can be translated into Sellsy credit notes so the back-office financial record follows the refund handled in ecommerce.
Yes. The refund flow can support draft credit-note creation when your finance team wants a review step before completing the document lifecycle.
Yes. Where useful, links to the Sellsy invoice or credit note can be written back to the Shopify order so support and operations teams can move from the ecommerce record to the corresponding back-office document.
Yes. When Sellsy is the inventory source of truth, stock movements managed in the back office can update the Shopify location used for ecommerce availability.
By default, paid and open orders are selected, with no restriction on fulfillment status. Payment, order, fulfillment and currency filters can be adjusted to match when your team wants a sale to become a Sellsy invoice.
Yes. The order flow can match or create Sellsy customers from Shopify billing and shipping details. Adding the shipping address to the Sellsy customer is optional; customer matching should be checked with representative orders during setup.
Consistent SKUs are important for identifying the same product in both systems. If a product cannot be matched, correct its information and check the affected document before reprocessing the order or refund.
Shipping refunds depend on mapping the Shopify shipping method to the appropriate Sellsy item or service. Check a refund that includes shipping during setup so the credit note reflects the intended shipping reference.
It runs on schedules: orders every 15 minutes with a 3-hour lookback, refunds every 30 minutes with a 2-hour lookback, and Sellsy stock movements hourly over the previous hour. Changes are processed on a later run when they meet the flow’s rules.
The stock flow updates a configured Shopify location. Define which location represents your ecommerce stock and keep Sellsy as the stock reference for that flow. A multi-location inventory model needs its own rules rather than assuming quantities are combined automatically.
Yes. Manual order and refund imports can be used for selected test records, backfills and controlled reprocessing. Review the Sellsy customer, product lines, shipping and totals on representative documents before extending automation to more orders.
Prepare access to both accounts with the required permissions, active Sellsy Billing for invoices and credit notes, consistent product SKUs and shipping mappings. Decide who validates documents, whether payments are recorded, and which Shopify location receives Sellsy stock.
Synchron provides operational visibility across order-to-invoice transfers, refund and credit-note activity, and stock synchronization so your team can see what moved between the systems and investigate anything that needs attention.
Keep exploring
Explore other supported integration pairs across marketplace, ecommerce and business systems.
Ready to connect?
Tell us how your team handles invoices, payments, refunds, delivery documents and stock today. We can shape the connection around the finance controls and operational responsibilities you want each system to keep.
