Quick Answer (TL;DR)
To integrate eBay with Microsoft Dynamics 365 Business Central, connect eBay's REST APIs (Inventory, Fulfillment, Finances) to Business Central through a prebuilt connector, an iPaaS platform, or a custom AL extension. The integration should import orders as sales orders, push stock and prices to eBay, write tracking back, and reconcile eBay payouts and fees automatically.
Key Takeaways
- Microsoft does not ship a native eBay connector for Business Central, so you choose between a prebuilt connector, an iPaaS platform, or a custom AL extension.
- A complete integration covers six data flows: items and listings, orders, stock levels, shipment tracking, payouts with fees, and returns.
- Payout reconciliation through the eBay Finances API is where most integrations break, so design it first, not last.
- In the US, eBay collects and remits sales tax as a marketplace facilitator, so that tax should never land in your own sales tax liability account.
- Plan for 3 to 8 weeks with a connector and 8 to 14 weeks for a custom build with complex variations or multiple warehouses.
Connecting eBay to Business Central is a project with one clear goal: every eBay sale should become accurate ERP data without anyone retyping it. Without that link, someone on your team copies orders from Seller Hub into sales orders, adjusts stock by hand after each sale, and spends month end trying to match eBay payouts to the bank. That works at 20 orders a day. At 200, it breaks. Listings oversell, tracking uploads late, and finance cannot explain why the payout is lower than gross sales.
We have connected eBay storefronts to Business Central for parts resellers, wholesale distributors and multichannel retailers. This guide shares the blueprint we follow on those projects, including the accounting and tax details that generic integration guides leave out. If you are new to the platform, our overview of is a useful starting point.
What Does an eBay and Business Central Integration Sync?
A complete integration moves six kinds of data. Leave one out and someone on your team will fill the gap with a spreadsheet.
| Data | Direction | eBay API | Business Central record | Suggested frequency |
| Items and listings | BC to eBay | Inventory API (inventory items, offers, item groups) | Items, item variants, item references | On change or hourly |
| Orders | eBay to BC | Fulfillment API (getOrders) | Sales orders, customers | Every 5 to 15 minutes |
| Stock levels | BC to eBay | Inventory API (price and quantity updates) | Item availability by location | Every 5 to 15 minutes |
| Shipping and tracking | BC to eBay | Fulfillment API (shipping fulfillment) | Posted sales shipments | When the shipment posts |
| Payouts, fees, refunds | eBay to BC | Finances API (transactions, payouts) | General journal, bank reconciliation | Daily |
| Returns and cancellations | eBay to BC | Post-Order API, Fulfillment API | Sales return orders, credit memos | Every 15 to 60 minutes |
eBay documents these endpoints in its , and Microsoft documents the Business Central side in the . Your integration lives between those two contracts.
Stop Re-Keying eBay Orders Into Business Central
Get a free eBay integration blueprint with field mapping, sync design and a fixed-scope estimate from certified Business Central engineers. Takes 30 minutes.
Does Business Central Have a Native eBay Connector?
No. Microsoft includes a free, native connector for Shopify inside Business Central, but there is no first-party eBay connector as of the 2026 release wave 2. Every eBay integration therefore runs through a third-party app, a middleware platform, or custom code. If you also sell on Shopify, our work shows how the native connector handles that channel, and many of the same item mapping rules carry over to eBay.
3 Ways to Integrate eBay with Business Central
| Approach | Best for | Typical timeline | Strengths | Limits |
| Prebuilt connector (AppSource or partner app) | One or two eBay stores, standard items, moderate volume | 3 to 6 weeks | Fast setup, vendor maintains eBay API changes | Less control over posting logic; fees often post as one net figure |
| iPaaS or middleware (for example Celigo, Boomi, Azure Logic Apps) | Sellers already integrating several systems | 4 to 10 weeks | Central monitoring, reusable flows across channels | Extra subscription; business logic lives outside Business Central |
| Custom AL extension with Azure Functions | Complex variations, multiple warehouses, detailed accounting | 8 to 14 weeks | Full control, native job queue and error log inside BC | Needs a developer to own upgrades and API changes |
Option 1: Prebuilt eBay connector
A connector is the fastest route when your catalog is straightforward. Before you buy, ask the vendor four questions. Does it support multi-variation listings? Does it post fees and payouts as separate lines or as one net amount? Can it allocate stock from specific locations? What happens, and who gets alerted, when an order fails to import? Vague answers usually mean customization later, which is one reason once real order volume arrives.
Option 2: iPaaS or middleware platform
Middleware makes sense when eBay is one of several systems you need to connect, such as a 3PL, a CRM and other marketplaces. You get one monitoring dashboard and reusable flows. The trade-off is that pricing, allocation and posting rules sit outside Business Central, so your finance team needs visibility into both tools. Our team typically recommends this route for sellers with four or more connected systems.
Option 3: Custom AL extension
A custom build gives you complete control. In our projects, the AL extension holds the mapping tables, a job queue entry polls eBay for new orders, and a dedicated error log page shows every failed record with a retry action. A small Azure Function manages OAuth token refresh and receives eBay notifications, including the marketplace account deletion notification eBay requires for production API keys. This is the right fit when your rules are unusual, and it is the core of our practice.
What about Power Automate?
Power Automate works well for alerts, such as emailing a team lead when an order fails to import. We do not recommend it as the main order pipeline for eBay sellers processing hundreds of orders a day, because run limits, retries and error handling become hard to manage at that volume.
Step-by-Step: How to Integrate eBay with Business Central
This is the sequence we follow on every eBay project. Teams that skip steps 1 to 3 are the ones that end up rebuilding the integration six months later.
Step 1: Audit your eBay listings and SKUs
Every eBay listing needs a SKU that matches a Business Central item number or item reference. Watch for one technical trap: listings created in Seller Hub or through older tools that use the Trading API are not visible to the Inventory API until they are migrated with eBay's bulk migrate listing call. Check this before you pick a tool, because some connectors only support one API family. Clean duplicate and inconsistent SKUs at the same time, using the cleansing approach described in .
Step 2: Decide the system of record for every field
Two systems editing the same field is the fastest way to corrupt data. Give each field exactly one owner.
- Business Central owns: item master, cost, price (through a channel price list), available quantity and locations.
- eBay owns: listing title, description, item specifics, category, and business policies for shipping, returns and payment.
- Rule of thumb: sync a field in one direction only. Never run a two-way sync on price or quantity.
Step 3: Map items, variants and conditions
An eBay multi-variation listing (an inventory item group in the API) maps cleanly to a Business Central item with item variants. Use item references to store the eBay SKU when it differs from your internal item number. Our guide to setting up item variants in Business Central covers the variant structure in detail.
Condition matters on eBay in a way it does not on most channels. If you sell the same part as new, used and refurbished, map each condition to its own item or variant. Otherwise a used unit can be shipped against a new-condition order, which leads to returns and defect marks on your seller account.
Step 4: Design the order import
- Poll, then listen. Query the Fulfillment API getOrders call with a last modified date filter every 5 to 15 minutes. Notifications are useful, but polling guarantees nothing is missed.
- Import paid orders only. Skip orders that are unpaid or on payment hold.
- Make imports idempotent. Store the eBay order ID in the External Document No. field and reject duplicates, so a retry never creates a second sales order.
- Choose a customer strategy. We usually recommend one customer per eBay store with a unique ship-to address per order. eBay limits the buyer contact data it shares, so creating a customer card per buyer adds clutter with little value.
- Map shipping and discounts. Post buyer-paid shipping to a G/L account line and handle seller-funded discounts as line discounts so margin reports stay accurate.
Step 5: Handle marketplace facilitator tax correctly
In the US, eBay calculates, collects and remits sales tax in states with marketplace facilitator laws, and the order data identifies that eBay-collected tax separately. If your integration lets Business Central calculate tax again, or posts eBay's tax into your own sales tax liability account, your tax returns will overstate what you owe. Set the eBay customer up so Business Central does not apply its own sales tax, and post the eBay-collected amount to a clearing account. Confirm the treatment with your tax advisor, especially if you also sell through eBay's UK or EU sites where VAT rules differ.
Step 6: Push available stock, not on-hand stock
The quantity you publish to eBay should be: stock in the locations assigned to eBay, minus open sales order demand from every channel, minus a safety buffer for fast movers. Sending raw on-hand stock is the number one cause of oversells we see. Our article on explains how to set buffers and sync frequency. On the Business Central side, batch your updates and respect Microsoft's , which throttle API calls per user.
Step 7: Write shipments and tracking back to eBay
When the warehouse posts a sales shipment, the integration should send the carrier and tracking number to eBay through the Fulfillment API immediately. eBay measures sellers on uploading tracking on time, so a nightly batch is not good enough. If a WMS or 3PL ships your orders, the tracking needs to flow from that system into Business Central first, as we describe in our guide to .
Step 8: Reconcile payouts, fees and refunds
eBay pays you net. Final value fees, Promoted Listings ad fees, shipping labels and refunds are all deducted before the money reaches your bank. The cleanest pattern we use treats eBay as a customer with its own receivable account, then posts each payout from the Finances API like this:
| Finances API data | Example | Business Central posting |
| SALE transaction | Order total including shipping | Sales invoice to the eBay customer (created by the order import) |
| Marketplace fees on the sale | Final value fee, ad fees | Debit Marketplace Fees expense, credit eBay receivable |
| SHIPPING_LABEL transaction | Label bought through eBay | Debit Freight Out expense, credit eBay receivable |
| REFUND transaction | Full or partial buyer refund | Sales credit memo against the eBay customer |
| Payout | Net deposit to your bank | Debit Bank, credit eBay receivable |
After every payout, the eBay receivable should net to zero for that payout period. Any remaining balance points to a missed fee, a dispute or an unimported refund, and you find it in minutes instead of at month end. Strong depends on this kind of clearing account discipline.
Step 9: Process returns and cancellations
A cancellation before shipment should cancel or delete the open sales order. A return after shipment should create a sales return order and a credit memo. Decide upfront where returned units go: back to sellable stock, into a used or refurbished variant, or into a quarantine location for inspection.
Step 10: Test real scenarios, then go live
Test in the eBay Sandbox and a Business Central sandbox environment with scenarios that mirror real trading, not just one happy-path order:
- Multi-quantity and multi-variation orders
- Combined orders with several line items from one buyer
- Partial refunds and full cancellations
- Two channels selling the last unit at the same moment
- Orders with eBay-collected sales tax and international orders shipped through eBay International Shipping
Run both processes in parallel for one to two weeks before switching off manual entry. Our covers the cutover steps.
Common eBay Integration Failures and How We Fix Them
- Oversells during sync lag: add safety buffers and sync fast movers more often.
- Duplicate sales orders: enforce a unique key on the eBay order ID.
- Expired OAuth tokens: eBay user refresh tokens expire after about 18 months, so monitor expiry dates and alert well before.
- Fees posted as one net figure: you lose visibility into channel margin. Post each fee type to its own account.
- SKU drift: someone edits a SKU in Seller Hub and the mapping silently breaks. Run a nightly mismatch report.
- Silent failures: without an error queue, nobody notices until a customer complains. Every failed record needs an owner and a retry button.
These mapping problems are not unique to eBay. We see the same patterns on other channels, as covered in why Business Central items won't sync to Shopify. After go-live, a plan keeps the integration healthy through eBay API changes and Business Central upgrades.
How Much Does an eBay and Business Central Integration Cost?
Costs depend on the number of stores, variation complexity, warehouse count and how much accounting detail you need. These are indicative ranges from US projects we have scoped:
| Approach | Software cost | Implementation cost |
| Prebuilt connector | About $100 to $600 per month | About $3,000 to $10,000 |
| iPaaS or middleware | About $500 to $2,000+ per month | About $8,000 to $25,000 |
| Custom AL extension | Azure hosting only, usually low | About $15,000 to $50,000, plus a support retainer |
For the bigger picture, see our breakdown of , or get a tailored figure with the .
Selling on Amazon, Shopify or Etsy Too?
Most eBay sellers are multichannel. Instead of building a separate point-to-point link for each marketplace, design one channel layer in Business Central with shared item references, channel price lists and location allocation rules. eBay then becomes one connection among several. We apply the same approach to , including Amazon FBA inventory in Business Central, and to handmade sellers following our Etsy integration with Business Central guide.
Once orders from every channel land in one ERP, turns that data into channel profitability reporting, and these Power BI sales dashboards for e-commerce show what that can look like.
Sync eBay and Business Central in Weeks, Not Months
Orders, stock, tracking and payouts flowing automatically, with zero oversells.
Is Your Business Ready for an eBay Integration?
Check these before you start:
- Your item master is clean, and every active eBay listing has a SKU.
- Warehouse locations are defined, and you know which ones serve eBay.
- Your chart of accounts has marketplace fee accounts and an eBay clearing or receivable account.
- A named person owns integration exceptions every day.
- You know your daily order volume, peak volume and number of eBay stores or sites.
If several of these are unclear, a short will surface the gaps before they become project delays.
Why Sellers Choose Trango Tech for eBay Integrations
As a , we design integrations around how your finance and warehouse teams actually work, not around what a connector happens to support. Every project starts with field mapping and posting design, includes a monitored error queue, and ends with documented ownership so your team is never dependent on guesswork. You can review examples of our delivery work in our .
Final Thoughts
An eBay and Business Central integration is not just an order import. Done well, it keeps listings accurate, prevents oversells, uploads tracking on time and reconciles every payout to the cent. Start with a clean SKU audit, pick the integration route that fits your complexity, and design the accounting before you write a single line of code. If you want a second opinion on your setup, for a free scoping session.
Frequently Asked Questions
Can I integrate eBay with Business Central without coding?
Yes. A prebuilt connector from AppSource or a Microsoft partner can sync orders, stock and tracking without custom code. You will still need to configure item mapping, locations and G/L accounts, and complex variation catalogs or detailed fee accounting may require some customization.
How often should inventory sync between eBay and Business Central?
Every 5 to 15 minutes suits most sellers. Fast-moving or low-stock items benefit from more frequent updates plus a safety buffer, so two channels cannot sell the last unit at the same time.
Can Business Central manage multiple eBay stores or international eBay sites?
Yes. Map each store or site to its own customer, price list and currency, and assign the warehouse locations that serve it. Keep separate fee and clearing accounts per site so reconciliation stays simple.
How do I record eBay fees in Business Central?
Pull transaction and payout data from the eBay Finances API and post each fee type, such as final value fees, ad fees and shipping labels, to its own expense account against an eBay receivable. The receivable should clear to zero when the payout reaches your bank.
Can Business Central create and update eBay listings?
Yes, through the eBay Inventory API, which creates inventory items and offers and publishes them as listings. Most sellers still manage titles, descriptions and item specifics in eBay, and let Business Central control price and quantity.
Can AI agents help manage an eBay integration?
They can help with exceptions, for example flagging failed orders or suggesting SKU matches. Our article on explains where agents add value today and where human review is still needed.
How long does an eBay and Business Central integration take?
Usually 3 to 8 weeks with a prebuilt connector and 8 to 14 weeks for a custom AL extension. Catalog cleanliness, number of stores, warehouses and accounting requirements have the biggest impact on timeline.
