Native Integration vs Middleware: What 'We Integrate' Means

By Bernardo Campelo, Forbes Business Council E-Commerce Leader and Founder of PrepVia, an Amazon SPN Certified prep center.

The word integrate can hide a spreadsheet. A prep center can tell a seller for months that it integrates with TikTok Shop while, behind the claim, an employee opens a spreadsheet, types the order numbers in by hand, and uploads the file to a portal twice a day. The calls, the emails, and the website never have to use the word spreadsheet. They only have to use the word integrate.

Ask prep centers whether they integrate with Amazon, Shopify, or TikTok Shop, and most will answer yes without a pause. The word covers three entirely different systems, and only one of them behaves the way a seller pictures the moment they hear it.

"We integrate with" says nothing about speed. It says nothing about who holds the authorization, and nothing about what happens the day the connection breaks. You have to ask those questions yourself, because the sentence will never volunteer the answer.

"We Integrate" Is Three Claims Wearing One Sentence

The phrase shows up in every RFP response, every sales call, and every line of marketing copy in this industry. A 3PL lists Amazon, Shopify, Walmart, and TikTok Shop under a single heading that reads Integrations, and a buyer reads that heading the way most people read it: as a promise that the systems talk to each other automatically, in something close to real time.

That assumption is often wrong, and it is wrong in three distinct ways, not one. A connection can be a native integration built on an official API. It can be middleware, a paid third-party connector sitting between the two systems. Or it can be a spreadsheet, moved by a person on a fixed schedule, wearing the vocabulary of software without any of its speed.

The difference matters most at the moment you are least likely to check it: when you are choosing a partner before you have any reason to distrust them. A seller evaluating a 3PL for Amazon FBA prep rarely asks which of the three levels sits behind the word integrate. This is the question worth asking before you sign anything, not after the first stockout.

Level One: Native Integration, Built on Your Own Authorization

A native integration runs on the official API the sales channel itself publishes: Amazon SP-API, the TikTok Shop Partner API, the Shopify Admin API. You, the seller, grant the connection from inside your own account, the same way you would approve any other authorized app. No password changes hands. No shared login exists anywhere in the process.

Once that authorization is granted, the two systems talk directly. Order data, inventory counts, and shipment status move without a person retyping a single field, and the delay is measured in minutes, not hours. A shipment confirmation on one side shows up on the other side close to the moment it happens, because there is no queue, no export, and no manual upload sitting between the two events.

This is also the level you can verify yourself in under a minute. Because you granted the authorization, you can open your own seller account and see the connected app listed there, with the scopes it was given and the date you approved it. You can revoke it yourself, at any time, without asking the 3PL for permission. That single fact, that you control the connection rather than the 3PL controlling it, is the clearest signal that Level One is real. It is the same mechanism behind any app you authorize on Amazon SP-API, and behind a working Amazon and Shopify fulfillment sync, where an order placed on your storefront reaches the warehouse floor without a person in between.

Level Two: Middleware, a Paid Connector Standing Between Two Systems

Middleware is the level most easily mistaken for Level One, because it is still automated. A 3PL pays a monthly license to a third-party integration platform, and that platform does the work of talking to both APIs so the 3PL does not have to build and maintain the connection itself. Data still moves without a person typing it in.

What changes is everything downstream of that convenience. The connector polls each system on its own schedule, which can run anywhere from every fifteen minutes to once an hour, so the near-real-time speed of a native connection is gone even though no human ever touches the data. A second, more important change is that you now depend on a company neither you nor your 3PL fully controls. If that middleware vendor has an outage, both your channel and your 3PL system can look completely healthy while nothing moves between them, and nobody may notice until a count is already wrong.

The question worth asking is simple: who pays for that license, and what happens to your connection if the 3PL switches vendors or lets the subscription lapse. A seller running multichannel prep across Amazon, Walmart, and TikTok Shop often has no visibility into that answer at all, because the license sits entirely on the 3PL side of the relationship, invisible on every invoice.

Level Three: The Spreadsheet Wearing an API's Clothes

The third level is the spreadsheet from the opening. A staff member logs into your seller portal, exports an order report or an inventory file, cleans it up, and uploads it into the 3PL's own system by hand. The schedule is usually fixed: twice a day, once a day, sometimes once per shift. From the outside, on a slide or a sales call, this can be described using the exact same word as Level One.

The tell is the delay. A spreadsheet process moves in hours, not minutes, and the gap between your last real update and the current moment is only as short as the time since the last upload. Every step also runs through a human hand, which means every step carries a human error rate: a missed row, a mistyped SKU, a file uploaded to the wrong folder. None of that shows up as a system outage, because there was never really a system there to begin with, just a person and a deadline. A prep center running TikTok Shop FBT prep on this level can look fully functional for months, right up until volume outpaces the person doing the export, which is one of the quieter entries on any honest list of prep center red flags.

The Three Levels, Side by Side

None of the three levels is announced by name in a sales conversation, so the table below is the shortcut. Read it as a set of questions to bring into your own vetting call, not as a judgment on any single provider.

Latency is the easiest column to fake in conversation and the hardest to fake on a screen. A provider can tell you their systems sync automatically and be technically correct about a Level Two connector that updates once an hour. Ask for the number in minutes, in writing, and you have already separated Level One from the other two.

Five Questions That Unmask Which Level You Are Buying

The fifth question does the most work. A native integration takes thirty seconds to demonstrate: open the seller account, point at the connected app, done. A middleware connection takes a bit longer but is still visible as a dashboard somewhere. A spreadsheet process is the one that produces a pause, a reschedule, or an answer that starts with "let me check with the team." Put the sync frequency and the audit rights in writing before you sign anything; the clauses in a prep center agreement checklist exist for exactly this reason. Treat this whole exercise as one part of a broader process for choosing a prep center.

Why the Gap Widens the Moment Volume Grows

At low volume, a twice-daily manual sync can look completely fine for months. One channel, a modest order count, and a spreadsheet upload every morning and every evening keeps pace well enough that nobody notices the gap. That is why the problem can go unnoticed for so long. A quiet volume hides a slow process the same way a quiet week hides a weak receiving team.

The moment you add a second or a third channel, or the moment your existing channel triples during a peak season, that fixed schedule stops being invisible and starts being the ceiling on how fast you can react. A native integration scales without adding headcount, because the API does not get tired at hour ten of a shift. Middleware scales too, but usually at the cost of a higher tier on the connector subscription. A spreadsheet process does not scale at all. It simply asks the same person to work later into the night, until the errors start arriving faster than the corrections.

This is where the integration level stops being a technical detail and becomes a P&L detail. A shipment sitting unreceived because nobody updated the system in six hours reads exactly like the discrepancies covered in inbound shipment tracking, and a provider whose real turnaround depends on a person keeping pace with volume is not offering the SLA it thinks it is offering, a gap explored in full in why your prep center SLA does not mean what you think.

Frequently Asked Questions

What does "we integrate with Amazon" actually mean at a prep center?

It can mean any of three different systems. It can be a native integration running on the official Amazon SP-API, authorized directly from your seller account, moving data in minutes. It can be middleware, a paid third-party connector sitting between the two systems on its own polling schedule. Or it can be a person exporting and uploading files by hand on a fixed schedule. The phrase alone tells you nothing, which is why the question is worth asking directly rather than assumed from a website heading.

What is the difference between a native API integration and middleware?

A native integration is built directly on the official API the sales channel publishes, authorized from your own account, with no third party in between and no separate license fee to track. Middleware adds a paid connector platform between the two systems, which still automates the data transfer but introduces its own polling schedule and its own point of failure. Both move data without a person typing it in, but only one of them removes the extra hop entirely.

How can I tell if a 3PL integration is really a spreadsheet with an operator behind it?

Ask for the sync frequency stated as a number, not a word like automatic or seamless, and ask to watch one export and one import happen live on a call. A spreadsheet process will produce a round schedule such as twice a day, a pause before someone can demonstrate it, or an answer that defers to checking with the operations team. A native integration or a middleware connector can be shown on a screen in under a minute.

What happens when a middleware connector goes down?

Both endpoint systems, your sales channel and the provider's own system, can continue to look completely healthy while no data moves between them, because the failure sits with a third-party vendor neither side directly controls. This is why the question of who monitors the connector, and how fast they notify you of an outage, matters as much as the sync speed itself.

Who should hold the API authorization for a prep center integration?

You should. A native integration is authorized from inside your own seller account, the same way any other approved app is granted access, which means you can see exactly when it was approved and revoke it yourself at any time without asking permission. If a provider needs your password or a shared login instead of an authorization you control, that alone signals the connection is not built on the official API.

Does a native integration send data back to the seller, or only pull data out?

A properly built native integration moves in both directions. It pulls order and inventory data from your channel, and it pushes receiving confirmations, shipment status, and count discrepancies back to you. A one-way connection that only reports what it is doing without confirming what actually happened at receiving is a weaker version of the same claim, and worth asking about specifically.

Why does the integration level matter more for sellers running multiple channels?

Because inventory shared across Amazon, Walmart, and TikTok Shop only stays accurate if every channel updates close to the same moment a unit moves. A fixed manual sync schedule that looks harmless on one channel becomes a source of oversells and stockouts the moment a second or third channel is drawing from the same pool of stock, especially during a peak season when volume multiplies faster than a person can keep up with the exports.

Final Take

"We integrate with" is a sentence built to carry three different meanings without forcing anyone to specify which one applies. A native API connection, a paid middleware layer, and a spreadsheet with a deadline can all sit under the same word on the same website, and only one of them behaves the way a buyer pictures when they read it.

The fix is not complicated. Ask how often the connection actually syncs, in minutes or hours, not adjectives. Ask who holds the authorization and whether you can revoke it yourself. Ask what happens the day it breaks, and ask to see the screen, live, before you sign anything.

Ask to see the screen while you are still comparing providers, before volume forces the gap into view and you already depend on one.

A real answer to that question takes thirty seconds to show and cannot be faked on a slide. If a provider cannot show you the screen, you already have your answer about which level you were being sold.