Selling refurbished and graded stock breaks the assumptions Business Central was built on. Standard Business Central treats an item as a single quality of goods: one item card, one set of price list entries, one pool of available inventory. A refurbished operation does not work that way. The same SKU exists as Grade A, Grade B and Grade C at different prices, different warranty terms and different quantities, and a refurbished marketplace expects each of those to be listed, priced and fulfilled separately. Teams typically bridge that gap with spreadsheets — exporting stock nightly, uploading listings by hand, keying orders back in the morning, and reconciling marketplace fees against the bank statement weeks later. Overselling a grade that has already gone, or discovering a fee variance at month-end close, is the predictable outcome.\n\nECOSIRE builds a Business Central AL extension that closes that gap inside the system your finance team already trusts. The extension adds condition grades as first-class data: a grade table with codes and descriptions, table extensions on Item and Item Variant that carry the grade and its marketplace attributes, and grade-aware price list entries so each grade prices independently rather than through a discount hack. A listing export routine reads your item attributes, resolves them through a configurable category and attribute mapping table, and validates the result before publishing so a rejected listing is caught in Business Central rather than in the marketplace's error inbox.\n\nTechnically, the connector runs on codeunits scheduled through job queue entries — one for stock and price deltas, one for order import, one for settlement retrieval — each with its own throttle and backoff handling so the marketplace rate limits are respected rather than tripped. Orders land first in a staging table with the raw payload retained, then post into sales orders with the marketplace status mapped to your document workflow; the raw payload means a failed import can be replayed without asking the marketplace to resend. Event subscribers on shipment posting push carrier and tracking numbers back to the marketplace automatically. Settlement statements are parsed into general journal lines against fee, commission and shipping-cost accounts you configure, so the marketplace payout reconciles to a bank receipt instead of being explained in a spreadsheet. Everything is exposed through custom API pages on the standard REST API v2.0 / OData v4 surface, so Power Automate flows, Power BI reports and Dataverse virtual tables can read connector data without a second integration layer. Dedicated permission sets keep the marketplace configuration separate from day-to-day order processing.\n\nThis is a build-to-order product, not an AppSource download. After you request a quotation we run a scoping call to confirm your Business Central version and deployment model, the marketplace account and API access you hold, your grade taxonomy, and the chart-of-accounts structure the settlement entries should post into. That produces a written scope and a fixed quotation. Once you confirm scope, typical delivery is two to four weeks: we build against your version, deploy to your sandbox, run UAT with your own catalogue and a marketplace sandbox account, and go live only after you sign off the acceptance script.\n\nYou receive the full AL source in your own git repository — no runtime-only package and no vendor lock on the code. During the agreed post-go-live support window we fix defects and adapt the extension to marketplace API changes, and we recompile and regression-test it against Business Central release waves so an upgrade does not strand you.