This is a build-to-order extension, not an instant AppSource install. Typical delivery is about one working week depending on catalog size, the number of Fruugo countries/currencies and any custom field mapping. ECOSIRE scopes your requirements, builds the AL extension, then installs and configures it as a per-tenant extension directly on your Business Central environment with Job Queue syncs running before handover.

Every build includes a post-go-live support window for bug fixes and configuration help. Because it is a per-tenant extension, ECOSIRE keeps the AL source version-controlled and validates compatibility against new Business Central monthly/major releases. If Fruugo changes its API or you add countries, currencies or catalog rules, we extend the connector under a support or change-request agreement rather than you maintaining custom code yourself.

No. Fruugo identifiers (listing IDs, order references, country/currency mapping) are stored on native BC records via table extensions — there is no separate sidecar database. Sync state is also readable through the BC REST/OData v4 API if you want to surface it in Dataverse or Power BI.

Yes. Multi-currency and multi-country selling is core to the design. Products publish with per-market prices and localized descriptions, imported orders map to the correct currency and ship-to country, and you can configure tax and rounding rules per Fruugo country so documents match local expectations.

Shipment and tracking write-back is automatic — event subscribers on BC shipment/posting events push carrier and tracking numbers to Fruugo. Fruugo returns are imported and captured as Return Orders or Credit Memos in Business Central so your finance team has an accurate, reconcilable record.

Access to your Business Central environment (a sandbox to begin), your Fruugo merchant/API credentials, a sample of your catalog with the countries and currencies you sell in, and your tax/shipping rules. We start in a sandbox, validate end-to-end, then deploy to production.