This is a build-to-order extension, not an instant AppSource install. A typical Wayfair connector takes about one working week depending on whether you run drop-ship, CastleGate/WGE wholesale, or both, and how complex your EDI partner profile and SKU mapping are. The process is: discovery and scoping of your Wayfair selling model and BC setup, development in AL against your sandbox, end-to-end UAT with real test orders, then a supervised production go-live. We confirm a firm timeline in writing after the scoping call before any work starts.

ECOSIRE installs the extension as a per-tenant AL app on your Business Central sandbox first, then production — you do not have to deploy anything yourself. The $999 covers the build, installation, and initial go-live support window. After that we offer ongoing support and maintenance (Wayfair API/EDI changes, BC monthly and major-version updates, new SKUs or selling channels) on a separate agreed plan. Because you receive the AL source and repository, you are also free to maintain or extend it with your own team.

No. It is built entirely as a per-tenant extension using table extensions, page extensions, and event subscribers — the standard, upgrade-safe BC development model. We never modify the base app, so Microsoft's monthly service updates and major version upgrades continue normally. We do regression-test the extension against your sandbox ahead of major BC releases as part of a support plan.

Both paths are supported and we pick what matches your Wayfair trading-partner setup. Most order, inventory, and price flows can run over the Wayfair Supplier/Partner REST API; where Wayfair requires it, we implement the EDI document set (832/850/855/856/810/846) instead of or alongside the API. On the Business Central side, data moves through the native REST/OData v4 endpoints, and credentials are held in isolated storage with a sandbox/production toggle.

Inbound, we import Wayfair drop-ship POs and wholesale orders into BC. Outbound, we push inventory availability and price on a Job Queue schedule, and we write back ASN/shipment confirmations with tracking numbers when you post a Warehouse Shipment. Every inbound message is processed idempotently with a dedupe key, and failures land in an error log with retry/backoff — so a retried Wayfair payload never creates a second order, and a transient failure is visible and re-runnable rather than silently lost.