Etsy Marketplace Connector

The problem this solves

A maker business that outgrows spreadsheets and adopts SAP Business One usually keeps one habit far too long: someone opens the Etsy shop manager every evening and types receipts into the ERP by hand. It works at twenty orders a week. At two hundred it becomes the bottleneck that decides how fast the business can grow, and it introduces the exact errors that make month-end painful — a receipt entered twice, a personalisation note lost, a variation posted against the wrong ItemCode.

Etsy's data model does not map cleanly onto an ERP without deliberate work. A receipt can contain several transactions. A listing can have variations that your item master treats as separate items, or as one item with attributes. Personalisation arrives as free text that production genuinely needs. Fees are not one number: listing fee, transaction fee, payment processing fee, offsite ads fee, currency conversion, plus shipping label purchases — and they settle through a payment account on Etsy's schedule, not on yours. Post that as a single lump sum and your gross margin per item becomes fiction.

Stock is the quieter problem. Handmade and small-batch inventory is finite. If the ERP knows a component is gone but the Etsy listing does not, you sell something you cannot make on time, and on Etsy a late dispatch is a review problem.

What ECOSIRE builds

ECOSIRE builds a per-tenant SAP Business One add-on and integration service for your Etsy shop. Nothing here is downloaded ready-made — it is scoped against your listings, your item master and your finance treatment, then built and installed into your company database.

Receipts into real SAP B1 documents

Etsy receipts are pulled on a schedule through the Etsy open API and posted through the SAP Business One Service Layer as genuine documents. A receipt becomes a Sales Order against a marketplace Business Partner — one channel-level Business Partner, or one per buyer if you want per-customer history — with the Etsy receipt ID, shop ID, buyer name and payment method held in header UDFs. Each transaction on the receipt becomes a line, mapped from the Etsy listing ID and variation to your ItemCode through a mapping table stored in a UDT.

Personalisation text and buyer notes are carried onto the Sales Order line free-text and into a UDF, so the pick list your workshop prints contains the instruction the customer actually gave. Dispatch creates a Delivery document with tracking; the A/R Invoice posts at the recognition point you nominate during scoping.

Listings and inventory

Available quantity is calculated from your chosen SAP Business One warehouses and pushed to the matching Etsy listings on an interval you set, with optional per-listing rules stored in a UDT — a fixed cap, a shared pool, or a made-to-order listing that is never quantity-driven at all. Where a listing has variations, quantity is pushed per variation against the mapped ItemCode. Price pushes from a nominated Price List are optional and guarded by a floor value so a bad price update cannot publish below cost.

New listings are not created blindly. Where listing creation or update is in scope, it runs from item master data you approve, with a review step rather than an automatic publish.

Fees, payment account and reconciliation

Etsy fee types are captured separately and posted to the G/L accounts your accountant nominates — listing, transaction, payment processing, offsite ads, regulatory operating fee, currency conversion and shipping label purchases. Amounts held in the Etsy payment account are posted against a clearing account and cleared when the deposit lands, so a bank deposit can be matched to the receipts and fees that produced it rather than accepted as an unexplained net figure. Where you sell in a currency other than your local currency, the connector records both the transaction currency amount and the converted amount so exchange differences are visible rather than absorbed.

Returns, cancellations and refunds

A cancelled receipt closes the Sales Order if nothing has shipped. A refund after dispatch creates a Return document where goods come back, and an A/R Credit Memo for the money, with the Etsy refund reason and case reference stored in UDFs.

Control and error visibility

A UDO-based control screen in the SAP Business One client lists every synchronised receipt with its state, last sync attempt and the actual API error when something fails, plus a manual retry. Approval procedures can gate connector-created documents where your finance team wants a human check. Crystal Reports layouts for Etsy channel sales, fee analysis and deposit reconciliation can be included where reporting is in scope.

Who this is for

Makers, small brands, jewellery and craft businesses, print-on-demand operators and boutique manufacturers who have adopted SAP Business One as the back office while Etsy remains a primary sales channel. It suits businesses with real inventory or components to track, meaningful order volume, and an accountant who wants margin per item rather than a single marketplace revenue line.

If you fulfil a handful of orders a month, manual entry is still the cheaper answer and we will tell you so on the call.

How delivery works

1. Scoping call. We review your shop, listing and variation structure, how variations map to your item master, order volume, warehouse setup, personalisation requirements, the fee lines your accountant needs separated, currency handling and your revenue-recognition point. We confirm your SAP Business One version, database platform and hosting.

2. Fixed quote. A written scope and a fixed price, issued before development starts. Anything outside the base build — listing creation, multi-shop, extra reports — appears as a named line item.

3. Build. Development against the Etsy open API and the SAP Business One Service Layer, with DI API used where document behaviour requires it. UDFs, UDTs and UDOs are created by an install routine.

4. Install into test, then production. Installed into your test company database first and run against your real receipts, including a return and a settlement period. You sign off document creation, fee posting and inventory behaviour there before the production company database is touched.

5. Support. A post-go-live support window covers defect fixes and Etsy API changes. Continued support beyond it is a separate agreement.

Typical lead time from signed quote to production install is two to four weeks, driven mainly by how complex your variation-to-item mapping is and how quickly API access for your shop is approved.