Puente OS
Back to resources
Puente OS vs· 21 min read· Cris Ugarte, CEO of Puente OS

Puente OS vs Multivende: What Each One Solves and How They Work Together

Multivende and Puente OS work on two layers of a multichannel operation, and companies use them together. Multivende is a marketplace integrator: it centralizes your channels' catalog, stock, prices, orders and shipping on a single platform. Puente OS builds and runs what happens around that sync: it reconciles what each marketplace pays out, matches receipts and credit notes, tracks every return, calculates margin by channel and brings the exceptions to your team. Puente connects to Multivende through a native connector and its API. Multivende syncs your channels; Puente runs what happens next and closes every sale end to end, with a system tailored to your operation that Puente's Growth Ops team builds with you and maintains.

Puente OS vs Multivende: What Each One Solves and How They Work Together

A marketplace integrator is a platform that connects your sales channels (marketplaces like Mercado Libre or Falabella, plus your own online store) with your systems, and keeps catalog, stock, prices and orders in sync across them. Puente OS is the platform that builds the systems that run your business: apps, workflows, databases and agents that read from your systems, cross-reference the information none of them holds in full, decide on your rules and execute the action inside them. The integrator moves data between channels, and Puente OS does the work that data creates.

I'm Cris Ugarte, CEO and co-founder of Puente OS. We work with retail, eCommerce and logistics companies in Chile, Peru and Mexico, and Multivende comes up often in our conversations with multichannel sellers: it's the integrator many of them already run. The next question is almost always the same: does Puente do the same thing?

My answer is that they do jobs that chain together. Multivende keeps every sale in sync across all your channels. From there a second operation begins: collecting what each marketplace settles, matching tax documents, tracking returns and knowing how much you made on each channel. Here I go through what each one does, with public sources for everything I say about Multivende, and how they connect in a real operation.

What is Multivende and what does it solve?

Multivende is an omnichannel integration platform for eCommerce: from a single dashboard you manage your marketplaces, your own store, your logistics operators and your management systems. Its website sums it up in the headline "Manage multiple marketplaces on a single platform" and states that over 500 companies use it every day.

Its modules, according to its features page:

  • Catalog. Each product's name, description, images and attributes, standard or customized by channel, with your categories mapped to each marketplace's. Products are created and edited in bulk, according to its Mercado Libre integration.
  • Inventory. One or more warehouses, assigned by channel, with stock synced in real time and deducted automatically on every sale.
  • Pricing. Single or channel-specific price lists, and special prices for marketplace campaigns and events.
  • Sales. Orders from every channel in one place, with a repository of electronic receipts and invoices that go out to the customer automatically on supported channels.
  • Logistics. Shipping labels, dispatch guides and order statuses synced for the customer, plus in-store pickup and picking and packing files, according to how it works.
  • Reporting and control. Sales and product reports, a dashboard with order status, delivery times and sync status, and users with different permission levels.

Its coverage is broad:

For technical teams, Multivende publishes a REST API with six integration dimensions: catalog, stock, prices, orders, tax documents and logistics. Mercado Libre recognized it as a Platinum partner in Chile in 2020, according to UDD Ventures, and Multivende earned ISO 27001 certification, according to Hackmetrix, the consultancy that guided it through the process. Among the case studies it publishes, one brand says it connected 16 marketplaces.

The same catalog, the same stock and the right price on every channel: that is Multivende's job.

What is Puente OS and what does it solve?

Puente OS is the platform that builds the systems that run your business. In your stack it is the system of action: it reads from your systems, Multivende included, cross-references the information none of them holds in full, decides on your rules and executes the action inside them.

What it builds comes from four pieces:

  • Databases that bring together context from several systems: the order, its receipt, its settlement and its return in a single record.
  • Workflows with explicit, auditable rules that start on their own when data changes or at a set time.
  • Agents for the steps that take judgment, like an ambiguous complaint or a discrepancy that needs investigating.
  • Apps where your team reviews, decides on and approves the exceptions.

With Puente OS you describe in natural language what your operation needs and get software running: apps, workflows, databases and agents. Puente's Growth Ops team builds each process with you and maintains it, and each one reaches production in 2 to 4 weeks. Puente acts on your systems, and where the operation lives in spreadsheets, it also keeps the record.

The discipline behind it is autonomous operations design: designing your operation so the repeatable work runs on its own, on your rules, and your team decides what takes judgment. For a closer look at the layer, see what a system of action is.

What happens to a sale after Multivende syncs it?

The work of closing it begins: collecting it, documenting it, reconciling it and measuring what it left you. Each marketplace settles on its own calendar and in its own format, and every receipt has to reach the SII, Chile's tax authority. Here is what the official sources say:

Closing a sale means cross-referencing all of that: the order against what the marketplace paid, the receipt against the sale and the credit note against the return. That work grows with the operation: every channel you add brings one more settlement for your team to match by hand, and online sales in Chile keep growing, according to the Santiago Chamber of Commerce. That cost has a name: the coordination tax.

How do Puente OS and Multivende compare, feature by feature?

Multivende covers the sync between channels, and Puente OS covers the processes that use that data to close, control and decide. Dimension by dimension:

  • Catalog. Multivende: creates and edits products in bulk, with categories mapped to each channel. Puente OS: works on top of that catalog, for example with an agent that enriches product listings in bulk and an App to review them before they go live.
  • Stock. Multivende: syncs stock in real time across channels and warehouses, with automatic deduction on every sale and inventory alerts. Puente OS: brings stock from your ERP into Multivende when that step needs an integration, with bulk updates through its connector.
  • Pricing. Multivende: price lists by channel and special prices for campaigns. Puente OS: decides the price on your rules, such as a minimum margin or a competitor's price, and executes it on the channel.
  • Orders. Multivende: brings orders from every channel into one place. Puente OS: takes each order through its full cycle (sale, receipt, shipping, payment and return) and flags the one that drifts at any step.
  • Shipping. Multivende: labels, dispatch guides, statuses, in-store pickup and picking, with native couriers and logistics partners. Puente OS: applies your assignment rules, such as courier by zone, cost and insurance, and writes the label and tracking number back to the order.
  • Tax documents. Multivende: a repository of receipts and invoices, automatic issuing through its native Bsale Chile integration with a monitor that shows each sale's document status, integrations with partner invoicing systems and a tax documents API. Puente OS: matches each document with its sale, its return and its credit note, whether it comes from the integrator, your POS or a manual issue, and issues in your invoicing system the documents for channels that run outside the integrator, such as a B2B sale to a retail chain.
  • Payments and fees. Multivende: delivers each channel's order through its API, with its payments and, depending on the channel, the fee the marketplace reports, which is the starting point for reconciliation. Puente OS: cross-references that order with Mercado Libre's billing report, Falabella's account statement and your bank, and flags every discrepancy in fees, shipping or payment.
  • Returns. Multivende: syncs order statuses and works with logistics partners that specialize in returns and exchanges, such as Reversso. Puente OS: links each return with its order and its credit note in a single record and routes it to the team that resolves it. Example 1 shows how to design tracking for the window each marketplace gives you to dispute it.
  • Reporting. Multivende: sales and product reports, and a dashboard with order status, delivery times and sync status. Puente OS: margin for each sales line and each channel, calculated daily from the sale and its cost, which surfaces the lines selling at a negative margin.
  • Custom rules. Multivende: configuration of channels, warehouses, price lists and user permissions. Puente OS: encodes the rules your team applies from memory, such as a discount cap by channel, an approval above a certain amount or shipping priority for your wholesale customers, and routes each exception to a named person, with full context.
  • ERP. Multivende: native Bsale in Chile, 28 integration partners and its API for ERP, POS, invoicing systems and WMS. Puente OS: connects to your ERP through its API or by reading its database, and brings in the cost, stock and documents each process needs to cross-reference against the sale.
  • Artificial intelligence. Multivende: works with AI partners in its ecosystem, such as Databot and Wise CX for customer service, Doofinder for search and gopersonal for personalization. Puente OS: the AI is in how it gets built, because you describe in natural language what you need and get software running; in the operation, a model reads what arrives messy and an agent takes the steps that need judgment.
  • Who implements it. Multivende: a help center, support and Multivende Academy training programs, plus a network of 28 partner developers who build the integrations with your systems. Puente OS: the Growth Ops team builds each process with you, puts it live in production and maintains it.

How do Puente OS and Multivende work together?

Puente connects to Multivende and uses it as the source of orders, products and stock for all your channels, adds the other sources each process needs and writes back where it belongs. What already works in Multivende stays as it is, and Puente orchestrates the rest.

The connection has three paths:

  • The native connector. Puente OS has a Multivende connector to authenticate the account, look up an order, search for a product by SKU and update stock in bulk.
  • The Multivende API. It is publicly documented and opens with a developer account that Multivende enables. It is REST, with OAuth 2.0 authentication and a limit of 5 requests per second, and its documentation mentions checkout and dispatch order webhooks, which its training program teaches you to use to listen for events in real time. For every other operation, a workflow calls that same API over HTTP, at the pace the API allows.
  • Each channel's sources. Mercado Libre's billing report, Falabella's account statement, the documents from your invoicing system and the cost of each product recorded in your ERP. Whatever arrives as a file comes in through a spreadsheet upload with mapping rules.

Each marketplace publishes its settlement in its own report, so reconciliation cross-references the Multivende order with each channel's billing report. With that, a sale's path looks like this:

  1. An order enters Multivende, and a workflow brings it into Puente's database, on an event or at a set time.
  2. The workflow adds the receipt, the shipment and, once it arrives, the marketplace settlement.
  3. The rules check the amount charged against the amount settled, the fee applied against the fee agreed and the credit note against the return.
  4. What matches closes on its own, and the rest reaches the right person in an App, with the full order in view.
  5. Puente writes back where it belongs, such as stock in Multivende or the document in your invoicing system, with every action logged.

When your ERP and Multivende run separately, Puente can cover that step: a workflow reads stock from the ERP and updates it in bulk in Multivende through its connector, on a schedule.

What does it look like in a real operation?

It looks like a layer of processes that closes every sale and leaves your team what takes judgment. The first example is a reference design for a seller using Multivende; the other two are Puente OS customers who connect their channels directly to Puente and already run this kind of work.

Example 1: designing order-cycle reconciliation on top of Multivende

Take a Chilean brand that sells on several marketplaces and on its own online store, with Multivende at the center. Closing each sale cross-references several sources: Multivende, inventory, the receipt system, credit notes, shipping, each marketplace's report and returns. This is how you design it with Puente OS:

  1. A database links each order with its receipt, its shipment, its settlement and its return.
  2. Workflows load the sources: Multivende through its connector and its API, and the marketplace reports that arrive as spreadsheets, with mapping rules.
  3. Matching rules flag every case that falls out of line: a receipt that differs from its order, a payment waiting on its shipment or a shipment waiting on its delivery.
  4. An App shows each team its own work: finance sees payment discrepancies, operations sees stalled shipments and customer service sees returns to resolve.
  5. Each return carries the window the marketplace gives you to dispute it, and your team sees the ones about to expire first.

Multivende keeps syncing catalog, stock and orders. Puente closes the cycle on each one.

Example 2: orders and shipping labels at a multichannel electronics seller in Mexico

An electronics seller in Mexico runs without an ERP, and Puente has seven of its sales channels connected. Every order that comes in through the channels Puente ships follows its path on rules: the address is validated, the carrier is chosen by zone, cost and insurance, the label is generated and the tracking number is written to the order. Puente also consolidates 213,362 Mercado Libre orders via API into a single sales report.

Of the orders Puente ships, 97.9% get their shipping label with no human intervention: 37,815 labels generated that way as of August 2026. Generating the labels for a cutoff went from 5 to 7 hours to 15 minutes, and monthly volume grew 40% with the same operations team. Behind it are 20 apps and 75 processes, built in ten months by one person. It is the work that surrounds every multichannel operation: consolidate, decide on rules and execute.

Example 3: margin by line at a pet retailer in Chile

A pet retailer sells on four channels. A workflow calculates the margin of every sales line each day: as of August 2026 it had covered 247,626 lines, and 3,830 of them, 1.5%, showed a negative margin that nobody saw before. Prices are also executed from Puente: as of that date it had made 8,362 price changes in the retailer's online store.

Why choose Puente OS?

Because Puente OS builds and runs the complete system that closes every sale: apps, workflows, databases and agents on a single platform, connected to your systems, with a Growth Ops team that builds it with you, maintains it and adds one process after another. Six concrete reasons:

  • It closes every sale end to end. The order, its receipt, its shipment, its settlement and its return sit in a single record. What matches closes on its own, and every payment, fee or document discrepancy reaches the person who resolves it, with the full sale in view.
  • It connects every source the process needs, Multivende included, and writes back to your systems. Multivende's orders, each marketplace's report, your invoicing system, your ERP and your bank feed into the same process, and whatever arrives as a file comes in through a spreadsheet upload with mapping rules. Puente executes the action where it belongs: it updates stock in Multivende, issues the document in your invoicing system or writes the label and tracking number to the order, and logs every action.
  • It's built around your operation. Each process uses the pieces it calls for (apps, workflows, databases and agents) and runs on your rules: the discount cap by channel, the agreed fee by category or the shipping priority for your wholesale customers are written down, auditable and running on their own.
  • A team builds it with you and maintains it. Puente's Growth Ops team maps your processes, decides with you what happens to each exception, puts each process live in production and maintains it as your operation grows: a new channel, a new rule or a report that changes format.
  • Each process reaches production in 2 to 4 weeks, and the next one is added on the same platform. You start with reconciliation for your largest channel and continue with returns, margin by channel or the documents for channels that run outside the integrator, on the same connections and the same data.
  • Results are measured in production. At the electronics seller in Mexico from Example 2, 97.9% of the orders Puente ships go out with an automatically generated label, and monthly volume grew 40% with the same operations team. It all runs on 20 apps and 75 processes that one person built in ten months. At the pet retailer from Example 3, a workflow calculates the margin of every sales line each day: as of August 2026 it had covered 247,626 and surfaced 3,830 with a negative margin.

Multivende keeps every sale in sync across all your channels, and Puente OS builds and runs the work that sale sets in motion, until the sale is closed.

When does each one make sense?

Multivende fits when your challenge is being on many channels with the same catalog, the same stock and the right price, and Puente OS fits when the work that comes after the sale eats up your team's hours. With volume across several channels, companies use the two together.

  • Multivende, if you need to publish and maintain your catalog across several marketplaces and your own store, sync stock between warehouses and channels, and ship with the couriers and operators that already work with it.
  • Puente OS, if your team reconciles each marketplace's settlement by hand, matches receipts and credit notes in spreadsheets, chases returns or measures margin by channel at month-end. Also if you have business rules that live in your team's heads and you want them to run on their own.
  • Both, when Multivende already syncs your channels and your operation's next leap is having every sale close on its own, on your rules. It's the scenario we see often in our conversations with sellers who already use Multivende.

How do you start if you already use Multivende?

With a process that hurts and that uses what Multivende already syncs, such as reconciling one channel or matching receipts. With Puente OS, each process reaches production in 2 to 4 weeks.

  1. Pick the process. With volume, manual handoffs and a visible cost when it fails: the settlement from your largest marketplace is usually a good place to start.
  2. Take the baseline. Orders per month, hours spent reconciling each week and the share of orders that close right the first time.
  3. Connect the sources. Multivende through its connector and its API, with the developer account Multivende enables, plus the channel's settlement, your invoicing system and your ERP.
  4. Write down the rules your team applies from memory. For example: "if the fee charged differs from the agreed fee for that category by over 1%, the order goes to finance for review."
  5. Decide where each exception goes. The system resolves it, or it reaches a named person with full context in an App.
  6. Measure from the first week and add the next process: returns, margin by channel or the documents for channels that run outside the integrator.

That is autonomous operations design applied to a multichannel operation: the repeatable work runs on its own, on your rules, and your team decides what takes judgment. To choose which steps run on rules and which go to an agent, this guide on how to implement AI in your business can help.

Your ERP records what happened. Your BI shows you what happened. Puente makes it happen. We believe every company in Latin America can be operationally autonomous, and in a multichannel operation with Multivende at the center, that starts with closing every sale end to end, on your rules.

Key takeaways

  • Multivende is a marketplace integrator: it syncs catalog, stock, prices, orders and shipping across your channels, with over 500 companies using it and coverage in Chile, Mexico, Colombia and Peru.
  • Puente OS builds and runs what happens after the sync: payment and fee reconciliation, tax document matching, returns, margin by channel and exceptions.
  • Each marketplace settles on its own calendar: Mercado Libre bills in monthly periods split into two groups, and Falabella pays daily and invoices monthly. Closing a sale means cross-referencing those sources with the order, the receipt and the return.
  • Puente connects to Multivende through a native connector and its API, and writes back where it belongs, such as stock in Multivende or the document in your invoicing system.
  • What Puente OS adds is the complete system that closes every sale: apps, workflows, databases and agents on your rules, connected to the sources each process needs, with results measured in production, such as 97.9% of shipped orders going out with an automatically generated label at an electronics seller in Mexico.
  • You start one process at a time, in 2 to 4 weeks each, and Puente's Growth Ops team builds and maintains it.

Already use Multivende and want to see which part of your operation can run on its own? Let's talk about your processes, and we'll show you Puente OS running with cases like the ones in this article. Book a conversation with our team.

Frequently asked questions

Does Puente OS replace Multivende?

Puente OS works alongside Multivende. Multivende keeps catalog, stock, prices and orders in sync across your channels, and Puente connects to it to run what happens next: reconciliation, tax documents, returns, margin and exceptions. What already works for you stays where it is, and Puente orchestrates it together with your ERP, your invoicing system and each marketplace. What Puente adds is the complete system that closes every sale end to end, built on your rules by a Growth Ops team that maintains it, with each process in production in 2 to 4 weeks.

Does Puente OS integrate with Multivende?

Yes. Puente OS has a native Multivende connector to authenticate the account, look up orders, search products by SKU and update stock in bulk. For everything else, a workflow uses the Multivende API, which opens with a developer account that Multivende enables and covers catalog, stock, prices, orders, tax documents and logistics.

Does Multivende issue electronic receipts and invoices?

Yes, through a connected invoicing system. With its native integration, Bsale Chile issues the receipt or invoice for each order that comes through Multivende. It also works with partner invoicing systems like relBase, Facele and webFactura, stores documents in a repository that sends them to the customer automatically and offers a tax document API. Puente OS matches those documents against each sale and each return, and issues the ones for channels that run outside the integrator.

What is marketplace sales reconciliation?

It is the process of verifying that every sale you made on a marketplace was paid in full: that what the marketplace paid, minus its fee, shipping and the applicable charges, matches the order, the receipt and the returns. On Mercado Libre it runs on monthly billing reports, split between Mercado Libre and Mercado Pago; on Falabella, on an account statement with daily cutoffs and a monthly invoice. With Puente OS, a workflow cross-references those sources with each channel's order and brings your team only the discrepancies.

What does the SII require of marketplace sellers?

The SII is Chile's tax authority. Since 2021 the sales and services receipt (boleta) has been electronic and mandatory, and to issue it with the SII's free system you only need a current first-category business activity registration (inicio de actividades). The issuer sends the SII every receipt it issues, and the SII uses them to populate the Purchase and Sales Register. Since January 2, 2026, marketplaces must require the people who sell on them to have that registration, and the SII set up Mi Negocio Cumple to complete it. Check your case with your accountant.

Does Multivende use artificial intelligence?

Multivende works with AI partners in its ecosystem: Databot and Wise CX for customer service, Doofinder for search and gopersonal for personalization, according to its partners page. In Puente OS, the AI is in how it gets built: you describe in natural language what your operation needs and get software running, connected to Multivende.

External sources cited

Most of these sources are in Spanish, and quotes from them are our translation. Everything this post says about Multivende comes from its website, its public documentation or third-party publications, reviewed on October 9, 2026. Puente OS customer figures are production measurements as of August 17, 2026; label generation time comes from follow-up meetings with the customer.

Multivende

  • Multivende, home page: headline "Manage multiple marketplaces on a single platform"; over 500 companies use Multivende every day; names Chile, Mexico, Colombia and Peru.
  • About us (Multivende): describes itself as an omnichannel integration platform for eCommerce.
  • Platform features (Multivende): Catalog, Inventory, Pricing, Sales (with a repository of receipts and invoices and automatic delivery to the customer), Logistics, Reporting, Control Panel, User Control and an App Store for ERP, POS, WMS, PIM and OMS.
  • How it works (Multivende): shipping management with in-store pickup and picking and packing files.
  • Marketplace integrations (Multivende): Amazon, Coppel, Dafiti, Falabella.com, Grupo Éxito, Liverpool, Mercado Libre, Paris, Ripley, Sanborns, Sears, The Home Depot, TikTok Shop, Totalplay and Walmart.
  • Other marketplaces (Multivende): Apprecio, Happygift, Hites, Juntoz, Nelo, Soho Market, Entrekids and Outlepp, through the App Store.
  • Integrations (Multivende): own stores (Adobe Commerce, BigCommerce, Jumpseller, PrestaShop, Shopify, VTEX, WooCommerce) and native couriers (Alas, Chazki, Chilexpress, Envíame, Llegó, Shipit, Welivery, Treggo).
  • Logistics partners (Multivende): 20 logistics partners, including Reversso, which specializes in returns and exchanges.
  • Integration developers (Multivende): 28 partners that integrate ERPs, POS, invoicing systems and WMS, such as Defontana, Softland, SAP Business One, Odoo, Manager+, relBase, Facele, webFactura and BillMySales.
  • Industry partners (Multivende): AI partners such as Databot, Doofinder, GoBots, gopersonal and Wise CX.
  • Native Bsale integration (Multivende blog, Jul 30, 2026): presents it as a new native integration; with each order, Bsale issues the receipt or invoice, and stock from its branches syncs with Multivende's warehouses; includes a Bsale billing monitor showing the sync status of each sale's document, and direct support during setup; available for Bsale Chile.
  • Mercado Libre integration (Multivende): catalog with bulk product management actions, inventory with alerts, prices and discounts, sales and logistics; available for Chile, Mexico, Colombia, Peru, Argentina and Ecuador.
  • Integration dimensions (Multivende): six API dimensions (catalog, stock, prices, orders, tax documents and logistics), with a matrix against ERP, OMS, POS, PIM, invoicing system, logistics operator, WMS and fulfillment.
  • Multivende Integration Services (API documentation, published Feb 24, 2026): REST API with OAuth 2.0, which requires a developer account requested from Multivende; JSON responses, 50-item pagination and a limit of 5 requests per second. The public collection at dev.multivende.com includes the Checkouts and Checkout Payments resources, with marketplace charges in the checkout examples, and mentions checkout and dispatch order webhooks.
  • API training program (Multivende Academy): weekly workshops, "OAuth2 y Webhooks," to listen for events in real time, and "Ventas y DTE's" (sales and electronic tax documents), to query orders and issue tax documents via API; links to Multivende's help center and support.
  • Case studies (Multivende): among others, Alluma's, with 16 marketplaces connected.
  • Multivende (UDD Ventures, Mar 12, 2021): recognized as a Mercado Libre Platinum partner in Chile in 2020.
  • Multivende scaled its security and business with ISO 27001 (Hackmetrix): Hackmetrix guided Multivende through ISO 27001 certification. The post is undated and says the certification was obtained three years ago.

Marketplaces, SII and market

See Puente OS in your operation

Let's talk about your processes, and we'll show you Puente OS running.

Sign up
Back to resources