The problem this solves
Selling on eBay while running SAP Business One usually means two disconnected systems held together by spreadsheets. Someone exports an eBay order report every morning, retypes the buyer into a Business Partner record, keys a Sales Order, then guesses which warehouse the stock came from. Quantities on eBay drift away from the real on-hand figure in SAP, so you either oversell and take defect strikes, or you hold a safety buffer and lose sales you could have made. At month end the finance team cannot tie eBay's payouts to anything: gross sales, final value fees, promoted listing fees, shipping labels and refunds arrive as one net deposit, and the reconciliation is done by hand against a downloaded CSV.
The cost is not just labour. It is oversell penalties, unmatched cash in the bank account, VAT reported on the wrong document dates, and a management team that cannot see channel profitability because eBay revenue sits outside the ERP until someone posts a summary journal weeks later.
What ECOSIRE builds for you
ECOSIRE builds a per-tenant SAP Business One add-on that treats eBay as a first-class sales channel inside SAP. Nothing here is a shrink-wrapped product you download — we build the connector against your company database, your item master, your warehouse layout and your chart of accounts.
Order ingestion into real SAP documents
The connector polls the eBay Sell APIs for new and updated orders and writes them into SAP through the Service Layer (REST), with the DI API used where an object needs behaviour the Service Layer does not expose. Each eBay order becomes a Sales Order with the correct Business Partner, ship-to and bill-to addresses, item lines resolved by SKU to your Item Master Data, freight rows for buyer-paid shipping, and tax codes assigned by your rules. Buyer identity is stored on UDFs so eBay usernames, order IDs and transaction IDs are queryable in SAP without abusing the Remarks field. Where you prefer a single trading-partner model, orders can be posted against one marketplace Business Partner with the buyer detail retained on the document and on a linked UDT.
Inventory and listing synchronisation
Available quantity is calculated from your chosen Warehouses — in stock, committed and ordered are all readable, so you decide the formula rather than accepting someone else's. The connector pushes revised quantities to eBay on a schedule and on change, applies per-SKU buffers, and suppresses updates for items you flag as not-for-marketplace. Price updates flow from your Price Lists or from a dedicated marketplace price list, so eBay pricing never depends on someone remembering to edit two systems. Listing creation and revision are supported for the fields your catalogue actually uses: title, category, item specifics, condition, quantity, price, and image URLs sourced from your item attachments.
Fulfilment, tracking and returns
When you post a Delivery in SAP, the connector marks the eBay order shipped and uploads the carrier and tracking number so the buyer sees it and your seller metrics stay clean. Partial shipments map to partial fulfilments. eBay returns and cancellations are pulled back and staged as Returns and A/R Credit Memos for review, so no credit is posted to your ledger without a human approving it.
Invoicing, fees and settlement
Orders can be invoiced automatically or on your existing document flow, producing A/R Invoices with the correct series, tax and revenue accounts. Payout reports are imported and expanded into Journal Entries that separate gross sales, final value fees, ad fees, shipping labels, refunds and the net transfer, so the bank line matches a real deposit and the fee accounts carry the analysis your accountant needs. Multi-currency is handled through SAP's own rates on the document date.
Control, visibility and errors
Every synchronisation writes to a log UDT with the raw payload, the SAP document created and the result. Failures are visible rather than silent: a monitoring screen built as a UDO lists the queue, lets an operator retry a single record, and shows why a SKU did not match. Where a document should not post automatically — a high-value order, an unmatched item, a new buyer — an SAP approval procedure can hold it. Crystal Reports layouts are provided for channel sales, fee analysis and settlement reconciliation.
Who this is for
Distributors, brand owners and refurbishers already running SAP Business One who sell on eBay alongside their own store or trade channel. It fits sites with a few hundred to tens of thousands of active listings, single or multi-warehouse, on SQL Server or SAP HANA, on-premise or cloud-hosted. It is not for businesses that have no SAP Business One installation.
How delivery works
1. Scoping call. We walk your eBay account structure, SKU mapping, warehouse and tax setup, document flow and payout handling, and agree exactly which objects are in scope.
2. Fixed quote. You receive a written scope and a fixed price before any code is written. No time-and-materials surprises.
3. Build. ECOSIRE develops the connector against a copy of your company database, typically over one working week depending on catalogue complexity and how many document types are in scope.
4. Install in test. We install into your test company database first, run real orders end to end, and reconcile a real payout with you before anything touches live data.
5. Install in production. After your sign-off we install into the production company database, migrate the configuration, and supervise the first live sync window.
6. Support. A support window is included for defect fixes and eBay API changes that affect the delivered scope. Ongoing enhancement work is quoted separately.
Because this is built to order, you own a connector shaped to your process — not a configuration screen fighting to approximate it.