A build-to-order SAP Business One connector that pulls Mercado Libre orders into Sales Orders and A/R Invoices, pushes stock and price from your warehouses, and handles shipping labels and fiscal document linkage. Built to order by ECOSIRE for SAP Business One (build-to-order) — indicative price from $799.00 USD; request a quote for a scoped proposal.
A build-to-order SAP Business One connector that pulls Mercado Libre orders into Sales Orders and A/R Invoices, pushes stock and price from your warehouses, and handles shipping labels and fiscal document linkage.
Bajo pedido
Selling on Mercado Libre while running SAP Business One usually means two people and a lot of copy-paste. Someone opens the seller panel, reads the new orders, and re-keys each one into SAP as a Sales Order — customer name, item, quantity, price, shipping method. Someone else watches stock, because a unit sold in the branch this morning is still advertised as available on the marketplace this afternoon, and an oversell on a marketplace costs you reputation metrics, not just a refund.
Then there is the shipping flow. Labels are generated in the marketplace, printed from a browser, and matched by hand to a picking list that came out of SAP. The tracking number never makes it back into the Delivery document, so customer service answers "where is my order" by opening a second system. And in the countries where fiscal documents are mandatory, the electronic invoice has to be raised in SAP and its number, series and authorisation reference pushed back to the marketplace order — a manual step that is easy to miss and painful to correct.
None of this is a marketplace problem or an ERP problem. It is an absent integration.
This is a build-to-order SAP Business One connector. Nothing is pre-built or available for instant download — after a scoping call and a fixed quotation we develop it against your seller account, your item catalogue and your company database, then install it.
New and updated marketplace orders are pulled on a schedule and created in SAP Business One as Sales Orders. The buyer is resolved to a Business Partner — either matched to an existing record by tax identifier or email, or created under a marketplace-specific Business Partner group and series, per the rule you choose at scoping. Marketplace fields that have no native home (order id, listing id, pack id, buyer nickname, shipping mode) are carried in User-Defined Fields so they remain queryable and reportable. Cancellations and buyer-side changes are reflected back onto the SAP document or flagged for a human where the document has already progressed.
Available quantity is pushed from your nominated Warehouses to the marketplace listings, with a reserve buffer per item or item group so you never advertise the last unit of a fast mover. You choose the calculation — on-hand, on-hand less committed, or a per-warehouse subset — and whether a multi-warehouse total or a single fulfilment warehouse drives the listing. Price updates flow from the SAP Price List you nominate, with an optional marketplace uplift rule to absorb commission. The mapping between SAP Item Codes and marketplace listing identifiers is held in a User-Defined Table so it is visible and maintainable inside SAP rather than hidden in a config file.
Where the order uses the marketplace's own logistics service, the connector retrieves the shipping label and tracking data and attaches them to the SAP flow, so warehouse staff pick and pack from SAP and print the label from the same place. The tracking identifier and carrier are written to the Delivery document, which means customer service answers shipment questions without leaving SAP. Fulfilment status changes coming back from the marketplace update the SAP document status so the two systems agree.
On fulfilment the connector creates the A/R Invoice, applies the marketplace payment, and posts the corresponding Journal Entry. Marketplace commission and shipping charges can be posted to nominated G/L accounts so gross revenue and net settlement are both visible. Where an electronic fiscal document is required in your country, the connector links the fiscal number, series and authorisation reference against the marketplace order and stores those references in User-Defined Fields on the SAP document. The specific fiscal integration in your jurisdiction is confirmed and scoped on the call — we build against your country's actual requirement rather than assuming one.
Every synchronisation run writes to an audit User-Defined Table: what was pulled, what was created, what failed and why. Failures are queued for retry rather than lost, and an exception list surfaces orders that could not be created — an unmapped item, a missing tax identifier, a listing sold in a currency you have not configured. Approval procedures can gate anything you want a human on, such as auto-creation of a new Business Partner or an order above a value threshold.
The connector uses the SAP Business One Service Layer (REST/OData) for document creation and master data, with the DI API where an operation is better served there. Marketplace communication uses the official seller API with OAuth token handling and refresh managed by the connector. Mapping tables, sync state and the audit log live in User-Defined Tables wrapped in User-Defined Objects; marketplace metadata sits in UDFs on Business Partners, Sales Orders, Deliveries and A/R Invoices. The synchronisation service runs alongside SAP so it does not depend on a logged-in client.
Supported: SAP Business One 10.0 on Microsoft SQL Server or SAP HANA, on-premise or cloud-hosted. Delivered per tenant, per seller account.
SAP Business One sellers in Latin America running a marketplace channel alongside wholesale or retail: consumer electronics and accessories, auto parts, home and hardware, apparel, and any catalogue large enough that manual listing maintenance has stopped being viable.
1. Scoping call. We confirm your seller account and the API scopes available to it, your item-to-listing mapping approach, which warehouses feed availability, your Business Partner creation rules, your fiscal document requirement, and your G/L mapping for commission and shipping. 2. Fixed quotation. A written scope and a fixed price before any development begins. Typical lead time is 2 to 4 weeks from acceptance. 3. Build. Developed against your configuration and tested against the marketplace's test facilities and a test seller account. 4. Install in test. Installed into your test company database. We run order ingestion, stock push, label retrieval and invoicing against a controlled set of listings so you see the whole loop before it touches live inventory. 5. Install in production. After sign-off we install into production and go live on a limited set of listings first, then widen the catalogue once the sync is stable. 6. Support window. A defect-fix and configuration support period on the terms stated in your quotation.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
They spend the first hour of every day re-keying marketplace orders into SAP and the rest of it fixing the ones that were keyed wrong. Automated order ingestion with an exception list means they handle only the orders that genuinely need a decision, such as an unmapped item or a buyer with no tax identifier.
They get oversells because the marketplace listing does not know about this morning's counter sale, and their team prints labels from a browser while picking from an SAP list. Warehouse-driven availability with a reserve buffer stops the oversells, and label retrieval into the SAP flow puts picking and printing in one place.
They reconcile a marketplace payout against dozens of orders where commission and shipping have already been deducted, and separately chase whether the fiscal document was linked to each order. Posting commission and shipping to nominated G/L accounts, and storing the fiscal reference on the SAP document, makes the payout tie out and the fiscal trail auditable.
| Criterio | ECOSIRE | Construcción personalizada | Competidor |
|---|---|---|---|
| Marketplace orders created automatically as SAP Sales Orders | Incluido | Apoyo parcial | Incluido |
| Warehouse-driven availability push with per-item reserve buffer | Incluido | Apoyo parcial | Apoyo parcial |
| Shipping label and tracking written back to the Delivery document | Incluido | Apoyo parcial | Apoyo parcial |
| Fiscal document number and authorisation reference linked to the order | Incluido | Apoyo parcial | Apoyo parcial |
| Commission and shipping posted to nominated G/L accounts | Incluido | Apoyo parcial | Apoyo parcial |
| Item-to-listing mapping maintained inside SAP in a User-Defined Table | Incluido | No incluido | Apoyo parcial |
| Idempotent retry queue and exception list for failed synchronisations | Incluido | No incluido | Apoyo parcial |
| Built for your seller account, catalogue and country requirement | Incluido | Incluido | No incluido |
A build-to-order SAP Business One integration with your 3PL: order release, shipment and tracking confirmation, receipts and stock adjustments posted automatically, built to your provider's spec.
A SAP Business One add-on that syncs Amazon Seller Central orders, FBA inventory, settlements and returns into Sales Orders and A/R Invoices. Built to order for your company database after a scoping call.
A build-to-order B2B portal on top of SAP Business One letting wholesale customers reorder at their own contract pricing, check availability, track Deliveries and download A/R Invoices. Built for your catalogue and pricing after a scoped quotation.
One-click forward and backward genealogy across batches and serials in SAP Business One, with FEFO allocation, expiry control and recall reporting. Built to order for your company database after a scoping call and fixed quote.
Desde $799.00
Precio de partida: se presupuesta según su alcance