This is build-to-order. After a short scoping call we confirm your Etsy shop structure, item/SKU model and tax setup, then build and install the extension. A standard single-shop connector typically takes about one working week from scoping to production go-live, including a sandbox UAT cycle. We give you a firm timeline in writing before any payment beyond the initial scope; complex variation, multi-shop or heavy tax/customization needs extend it and we say so up front.

You get a defined post-launch window covering bug fixes and adjustments at no extra charge. Because the connector is a true per-tenant extension with no base-app modifications, it keeps working across Microsoft's monthly Business Central updates. If Etsy changes their Open API, or you want new features, that's covered by an optional ongoing support and maintenance plan. You also receive the full AL source, so you're never locked to us.

No. We install it directly on your Business Central environment as a per-tenant extension — built specifically for your shop and tenant. That means we can tailor item mapping, tax posting and listing logic to your exact setup instead of shipping a one-size-fits-all app. You own the code and the deployed .app.

Imports are idempotent: every Etsy receipt and transaction ID is stored on the BC record via table extensions, so re-running the Job Queue never creates a second order for the same receipt. All logic lives in extension objects and event subscribers — we never modify the base application — so monthly Microsoft updates won't break it.

Yes. Listings publish from BC Items with their variations (such as size and color) and Etsy personalization fields are captured on the sales document so your team sees buyer instructions. On tax, we map Etsy's collected sales tax and marketplace-facilitator amounts, plus shipping and discounts, to the VAT/sales tax posting groups and GL accounts you specify during scoping, validated together in the sandbox before go-live.