Orders → invoices
Turn eligible WooCommerce orders into Sellsy invoices while reusing the billing customer, order lines, quantities, prices, shipping, taxes, coupons and payment references already produced by the store.
WooCommerce sales, ready for the Sellsy back office
Move the ecommerce sale from WooCommerce into Sellsy without asking finance to reconstruct it. Synchron can turn eligible store orders into Sellsy invoices, match or create the customer, carry across the commercial detail behind the checkout, and let your finance team decide how far invoice validation and payment automation should go.
Keep the storefront flexible and the back office structured
WooCommerce gives merchants a highly flexible way to sell, which also means the financial meaning of an order can depend on store-specific statuses, tax rules, shipping methods, coupons and payment behaviour. Synchron carries that completed ecommerce context into Sellsy so the back office can work from a structured invoice and customer record instead of rebuilding the transaction from separate pieces.
Use your ecommerce lifecycle as the billing trigger, preserve the commercial detail behind the sale and keep finance in control of the final document
Connected workflows
This integration focuses on one important hand-off and does it thoroughly: turning the right WooCommerce order into a Sellsy financial record with the customer and transaction context needed by the back office.
Turn eligible WooCommerce orders into Sellsy invoices while reusing the billing customer, order lines, quantities, prices, shipping, taxes, coupons and payment references already produced by the store.
How it works
The hand-off starts with the ecommerce lifecycle your business already trusts and carries the order into Sellsy without stripping away the commercial context behind it.
The integration can focus on the order statuses that represent the point at which your business considers a sale ready for invoicing.
Billing information from the order can be used to find the existing Sellsy customer or create the customer context needed for the invoice.
Products, quantities, pricing, shipping, taxes, coupon context and payment references can travel with the order instead of being re-entered by finance.
Once the invoice exists, validation, payment recording and related Sellsy document handling can follow the level of automation your finance operation is ready to use.
Operational visibility
Because this integration creates financial documents, a missed order or incorrect hand-off deserves a clear operational trail. Synchron makes the transfer observable so teams can see whether the WooCommerce sale reached Sellsy and investigate the source context when it did not.
Keep the connection between the originating WooCommerce order and the Sellsy invoice process visible as finance takes over.
Test a known order, backfill historical sales or reprocess a corrected case without changing the business rules that govern the normal automated flow.
When customer, status, tax or order data prevents the expected result, your team can review the affected transaction in context before trying again.
Why Synchron.io
WooCommerce can be customised around the way a merchant sells. Sellsy is where the resulting customer and invoice records need consistency. Synchron bridges those two priorities without forcing either team to abandon the system built for its work.
Reuse the order data already captured online instead of asking finance to copy customer, product, shipping, tax and payment information into Sellsy.
Start invoicing from the WooCommerce order states that represent a real billing event for your operation.
Automate document creation without assuming invoice validation or payment recording should happen before your team is ready.
Use checkout identity and address information to support the Sellsy customer record behind each ecommerce invoice.
Give teams a visible integration trail for the WooCommerce orders that become Sellsy invoices and the cases that require review.
A WooCommerce order can move through several operational states before finance should act. Synchron lets the invoicing hand-off begin from the point that makes sense for your store rather than assuming every new order is immediately ready for the books.
Choose the WooCommerce lifecycle points that mean the customer order has reached the level of certainty your finance team expects before a Sellsy invoice is created.
Keep orders that are still moving through an earlier operational stage out of Sellsy until they meet the business rule used for invoicing.
If your WooCommerce operation uses its own status conventions or extensions, the invoicing model can be planned around the lifecycle your team already follows.
An invoice is more than an order total. Shipping, discounts, taxes and payment references all influence how finance understands the transaction. Synchron reuses that ecommerce context so Sellsy receives a document built from the sale that actually happened.
Use the order lines and product references from WooCommerce as the basis for the Sellsy invoice instead of rebuilding the basket manually.
Carry the delivery charges and discount context that changed what the customer paid so the back-office document reflects more than just the merchandise.
The integration can be configured around how your WooCommerce store represents tax and totals so finance can review Sellsy documents against the commercial source.
Where payment information matters to reconciliation or follow-up, the Sellsy record can stay connected to the payment context captured by WooCommerce.
Creating the Sellsy invoice and finalising it are separate decisions. Synchron can start by removing data entry while leaving finance with a review checkpoint, then support deeper automation once the output has been validated against your process.
Create the Sellsy document without forcing immediate validation so the finance team can inspect early imports and confirm the mapping is behaving as expected.
Once the process is stable, invoice validation can become part of the automated hand-off when that matches your internal controls.
If WooCommerce already contains the payment information finance relies on, the workflow can also create the corresponding Sellsy payment record rather than leaving a paid ecommerce sale looking unpaid in the back office.
Where your administrative workflow uses a Sellsy order document alongside the invoice, it can be created as part of the same hand-off instead of requiring another round of manual entry.
Finance should not have to guess which Sellsy customer belongs to a WooCommerce order. The integration can use the billing information captured at checkout to connect the transaction to the appropriate customer record and carry useful delivery context with it.
Use the WooCommerce billing identity to look for the corresponding Sellsy customer before creating a new record for the invoice.
If the customer does not yet exist in Sellsy, the order can provide the information needed to establish the financial record without a separate onboarding step.
Delivery-address information can be carried into Sellsy when finance, support or logistics teams need that context around the customer.
Sellsy records created from WooCommerce can remain easy to recognise and organise for reporting or operational follow-up.
Questions, answered
These are the practical questions teams ask when WooCommerce should remain the sales source while Sellsy takes ownership of invoicing and financial follow-up.
Your WooCommerce invoicing process has another rule?
Tell us which store orders should become invoices, how finance reviews them and which customer, payment or document details matter in Sellsy. We can discuss how the hand-off should fit around your existing process.
Yes. Synchron can turn eligible WooCommerce orders into Sellsy invoices while carrying the customer, order lines, pricing, shipping, tax, coupon and payment context needed by the back office.
Yes. The order lifecycle can be used to define which WooCommerce statuses represent a sale that is ready to enter the Sellsy invoicing process.
The workflow can use WooCommerce billing information to match the appropriate Sellsy customer and can create the customer context required for the invoice when no suitable record exists.
Yes. Automatic validation is optional, so teams can begin with review-first invoice creation and introduce further automation after the generated documents have been checked against the finance process.
Yes. Payment creation can be included when the WooCommerce payment information should be reflected in Sellsy as part of the financial hand-off.
Yes. A related Sellsy order document can be included when your back-office process requires it alongside the invoice.
The documented WooCommerce + Sellsy workflow currently focuses on importing WooCommerce orders into Sellsy invoices. Refund, credit-note and inventory synchronization should not be assumed for this pair unless they are added and confirmed separately.
Synchron keeps the order-to-invoice hand-off observable so your team can review which WooCommerce sales reached Sellsy, investigate exceptions and use controlled manual imports for testing, backfills or corrected cases.
Keep exploring
Explore other ways to connect marketplace, ecommerce and business systems with Synchron.
Bring your workflow together
Tell us which WooCommerce orders should trigger invoicing, how finance reviews documents and whether payment or related Sellsy records should be created automatically. We can shape the hand-off around the process your teams already trust.