Amazon connector for Business Central: Standard or custom?

Amazon connector for Business Central: Should you choose a standard or a flexible integration?

If you are searching for an Amazon connector for Business Central, it is tempting to ask one question:

“Which connector can link the two systems?”

A better question is:

“Which processes does the connection actually have to be able to handle?”

Because a standard connector can be exactly the right solution.

But it can also be the wrong one if the company’s setup is far from the standard.

When does a standard connector make sense?

A simple setup could for example be:

One Amazon marketplace.

Identical SKUs.

Business Central as the central ERP.

A simple inventory structure.

A clear order flow.

Here standard functionality can make sense, because the company gets a faster and more predictable implementation.

When does the standard start to feel tight?

Complexity typically grows if the company has:

• both FBA and FBM
• several marketplaces
• WMS
• 3PL
• several stock locations
• bundles and product mapping
• particular Business Central fields
• specific posting rules
• its own error and approval flows

Then the question becomes whether the connector can be adapted to the business, or whether the business has to be adapted to the connector.

Look beyond the feature list

A connector may advertise:

“Order sync”.

But what does that mean?

Can it handle your customer setup?

Dimensions?

FBA/FBM?

Cancellations?

Unknown SKUs?

Duplicates?

It is the details that determine whether the integration works in daily operations.

Monitoring is a feature

One of the most underestimated features in integrations is the ability to see when something does not work.

An order that never comes in is far worse than an order that fails visibly.

That is why you should assess:

How are errors logged?

Can data be reprocessed?

Who is notified?

Can you see the history?

What happens when Amazon or Business Central changes?

The Amazon SP-API has ongoing release notes and changes, and Microsoft maintains corresponding Business Central APIs. Amazon Developer Docs

That is why the connector’s maintenance model should be part of the decision.

Who owns the upgrades?

How are changes tested?

What happens to custom logic?

Total cost is more than the license

A cheap connector is not necessarily cheap if employees still:

• correct orders manually
• reconcile with Excel
• monitor stock themselves
• solve errors every week

Conversely, you should not build a complex custom solution for a problem that standard software already solves well.

When does an integration platform fit better?

If Amazon is only one system among many, it can be more relevant to think in terms of an overall integration architecture.

Amazon → Business Central
Webshop → Business Central
WMS → Business Central
3PL → Business Central

Instead of having a separate integration mechanism for every connection, the company can consolidate logic and monitoring.

Read more about Connectify’s Integration platform. Connectify itself describes the platform as a way of consolidating integrations and data flows across ERP, e-commerce, PIM and other systems.

The best connector is the one that matches the complexity

Standard is not bad.

Custom is not automatically better.

What matters is fit.

If 90 % of the need is standard, you should be careful about building 100 % custom.

If only 40 % fits the standard connector, on the other hand, it can become expensive through manual workarounds.

Are you in doubt about whether a standard connector is enough?

Get your Amazon and Business Central setup assessed

We can go through the specific flows before you choose an integration model.