A North American maker of personalized name badges, lanyards, and meeting & event supplies connected its Amazon marketplaces to Microsoft Dynamics 365 Business Central with BURQ iPaaS, an ecommerce ERP integration that eliminated manual order entry, automated settlement reconciliation, and unlocked a sales channel it couldn't run by hand.
Custom meeting & event supplies (personalized name badges, lanyards, and event credentials)
United States; selling on Amazon's Canada and Mexico marketplaces
Microsoft Dynamics 365 Business Central
BURQ iPaaS, the Folio3 ISV connector for Dynamics 365 Business Central connector and Amazon
Product sync, FBA + FBM order automation, inventory transfers, returns/refunds, and Amazon settlement reconciliation
The client is a United States–based manufacturer of custom meeting and event supplies, personalized name badges, lanyards, and event credentials made to order for conferences, trade shows, and corporate events. Almost every item it ships is customized: a specific name, a line of ribbon text, a chosen font, a buyer's exact specification.
The business runs its financials and back-office operations on Microsoft Dynamics 365 Business Central and sells to customers through Amazon's Canada and Mexico marketplaces, fulfilling orders through both Fulfillment by Amazon (FBA) and Fulfillment by Merchant (FBM). Its end customers are largely event planners and organizers working against fixed, time-sensitive event dates, which makes order accuracy and turnaround time commercially critical, not just operationally convenient.
40–50 days of skilled finance labor saved per year by automating Amazon settlement reconciliation, roughly one full workday recovered every week
Per-order processing cut from 5–10 minutes of manual entry to near-instantaneous sync, letting the team absorb 2,700+ orders in the first partial year with no new data-entry hires
100% data accuracy on custom order details flowing from Amazon into the ERP, removing the typos that drove production errors, waste, and returns
A new Amazon FBM sales channel opened up, expanding the catalog from a handful of standard items to a full range of customizable products
A stable integration now supports a projected 3–4x increase in order volume in the year ahead, without adding operational headcount
The company makes personalized products, name badges, lanyards, and event credentials, where almost every order carries custom details: the text printed on a ribbon, a specific font, and a buyer's exact specification. That customization is the product. It's also exactly the kind of data that breaks when a human has to retype it.
The deeper cost wasn't the hours. It was the ceiling. Manual entry meant the company effectively couldn't list its customizable catalog on Amazon's FBM channel at any real scale; the custom-attribute data was too complex and too error-prone to transcribe by hand, so the Amazon presence stayed limited to a couple of standard items. The team couldn't market aggressively because they couldn't trust the back office to keep up. They needed a full, end-to-end integration covering sales, fulfillment, settlement, and returns, not another partial bridge.
The company sold on Amazon's Canada and Mexico marketplaces and ran its financials and back office on Microsoft Dynamics 365 Business Central. Between the two, there was nothing. No integration connected Amazon to Business Central, so the seams were stitched together by people.
Every Amazon order was keyed into Business Central by hand. Inventory counts, pricing, and returns drifted out of sync. Refunds lagged, and customers noticed. And at the end of each cycle, someone on the finance team sat down to reconcile Amazon's settlement reports against Business Central line by line, a task that ate roughly a full day of skilled work every week.
The company chose Folio3’s BURQ iPaaS for reasons that map directly onto what a buyer in this position worries about.
First, the integration risk was already retired. BURQ iPaaS, Folio3's integration platform, supports Amazon-to-Business Central integration out of the box, so the core connection wasn't a custom build from zero. Second, Folio3 has proven Dynamics 365 Business Central integration experience and real domain depth in both Amazon fulfillment models, FBA and FBM, which matters because the hard part of this project lived in the FBM customization flows. Third, the platform could be tailored to the company's specific operational quirks rather than forcing the business to bend around the software.
The company came in with high-level requirements rather than a finished spec. Folio3 led the discovery, clarified the business cases, and shaped the final integration flows, so the team didn't have to already know the answer to get the right one built. The result was a single marketplace integration that treated Amazon and the ERP as one connected system rather than two systems a person shuttled data between.
A six-person Folio3 team (solution engineering, QA, and project management) delivered the integration on BURQ iPaaS over roughly two to three months. The Amazon Seller Central integration connected to Business Central across the full order lifecycle, using Amazon's Seller Central APIs to move data both ways.
The build automated the parts that had been manual and brittle. Products sync between Amazon and Business Central via SKU matching. Sales orders import automatically and route themselves by fulfillment type, unshipped orders into FBM, shipped orders into FBA — with variant handling for customized FBM items. The buyer's customization notes flow through as comments on the sales lines, so the people who actually make the product see exactly what was ordered. Amazon "in-transit" stock generates transfer orders in Business Central. Shipment and tracking updates flow back to Amazon automatically. Returns generate the right financial document on each side, and settlement charges post through automated cash receipt journals and credit memos. Every process is logged, with retry and error-handling built in.
A custom field, purpose-built to carry Amazon's actual fulfilled quantity into Business Central, closed a fulfillment-accuracy gap that off-the-shelf mapping would have missed. That kind of detail is the difference between an integration that demos well and one that survives contact with real orders.
The reconciliation alone gave us back a full day a week, and the data coming in from Amazon is finally clean. We can put our real, customizable catalog on Amazon now and actually scale it, that wasn't possible when everything went in by hand.
ERP and Database Manager.
A renowned Event-Supplies Manufacturer
The clearest win landed in finance. Automating Amazon settlement reconciliation eliminated roughly one full day of manual work every week, an estimated 40 to 50 days of skilled labor saved per year. The reconciliation that used to be a weekly slog now runs in the background.
Order handling changed shape entirely. What took 5 to 10 minutes of manual entry per order became near-instantaneous sync, and the company absorbed more than 2,700 orders in the first partial year without hiring a single additional data-entry person. The work didn't get redistributed; it got removed.
Accuracy followed. By eliminating the manual transcription of custom ribbon text and font selections, the integration delivered 100% data accuracy from Amazon into the ERP, which in a custom-manufacturing business is not a vanity metric. Every typo avoided is a misprinted badge not made, a return not processed, and material not wasted.
Solving the complex data mapping for custom product attributes unlocked the Amazon FBM sales channel, letting the company expand its Amazon catalog from two or three standard items to a wide range of customizable products it simply couldn't have listed and fulfilled by hand. Automated shipment-tracking updates kept data flowing to Amazon on time, protecting the company's seller rating and removing the risk of account suspension from late manual reporting. And because orders now synchronize in real time instead of being entered the next day, the production team can start manufacturing custom orders immediately.
If your team is keying Amazon orders into Business Central by hand, reconciling settlement reports line by line, or holding back a customizable catalog because the data is too messy to transcribe, there's a better way. BURQ iPaaS is an e-commerce ERP integration platform that connects Amazon Seller Central to Microsoft Dynamics 365 Business Central across the full order lifecycle: products, FBA and FBM orders, inventory, returns, and settlement.
Amazon connects to Dynamics 365 Business Central through an integration platform (iPaaS) that syncs data between Amazon Seller Central and the ERP. BURQ iPaaS automates this across the full order lifecycle, products, FBA and FBM orders, inventory transfers, returns, and settlement, so orders no longer have to be entered into Business Central by hand.
Yes. A complete Amazon fulfillment integration routes orders automatically by fulfillment type, unshipped orders into FBM, and shipped orders into FBA, and handles each flow end-to-end. In this project, BURQ iPaaS also supported variant handling for customized FBM items and synced buyer customization notes as comments on the sales lines.
It depends on scope and customization, but a full end-to-end Amazon Business Central integration covering sales, fulfillment, inventory, returns, and settlement can be delivered in roughly two to three months. The project in this case study was built by a six-person team across solution engineering, QA, and project management.
Yes. The integration posts Amazon charges into Business Central through automated cash receipt journals and credit memos, which removes the manual line-by-line matching of Amazon settlement reports against ERP records. In this case, that automation saved an estimated 40 to 50 days of skilled finance labor per year.
Yes, with the right data mapping. Custom products carry extra attributes, personalized text, fonts, and variant details that must flow accurately from Amazon into the ERP. Solving that mapping is what lets this manufacturer list its customizable catalog on Amazon's FBM channel and reach 100% data accuracy from Amazon to Business Central.
It can. BURQ iPaaS supports both real-time, event-driven synchronization and scheduled polling. Real-time order sync eliminates next-day data-entry delays, so production can begin on custom orders immediately rather than waiting for a manual batch to be keyed in the following day.
BURQ iPaaS is Folio3's integration platform as a service (iPaaS platform). It connects enterprise applications, such as Amazon Seller Central and Microsoft Dynamics 365 Business Central, and synchronizes data and workflows between them, with built-in error handling, retries, and logging. It is the platform used to deliver the Amazon Business Central integration in this case study.
Get in touch for more information and clarifications
