Total Fishing Tackle
Cross-border selling with local currencies and checkout, on a Hyvä store with more than 11,000 products.
Orders, stock, prices and invoices kept in step, so the shop and the books agree without re-keying.
Two-way integration between Microsoft Dynamics 365 Business Central and Magento Open Source, Adobe Commerce or Mage-OS, delivered with our partner n.vision. For merchants who run Business Central for finance and stock and want the store to agree with it. You get a field-by-field scope and a written estimate once we have examined both systems.
What finance and operations teams tell us before an integration.
Someone copies every web order into Business Central by hand each morning.
Hours a week spent on typing, and every typo becomes a stock or ledger problem. Orders should arrive on their own.
The website sold something the warehouse ran out of last week.
Stock on the store is a snapshot nobody refreshes. It needs to come back from Business Central on a schedule.
We change a price in Business Central and then have to change it again in Magento.
Two places to keep in step means one of them is wrong. Prices should have one source.
Six parts, each agreed field by field before it is built, each monitored once it is live.
Every web order created as a sales order, mapped the way your finance team expects to see it.
Available quantity per item and location, on a schedule agreed with you.
Base, customer-specific and group prices taken from Business Central price lists.
Accounts, trade customers and addresses, with the system of record agreed per field.
Posted invoices, credit notes and tracking back against the order, visible to the customer.
Failures queued, logged and alerted, retried where transient, reported monthly.
Cross-border selling with local currencies and checkout, on a Hyvä store with more than 11,000 products.
… The quality of their work is second to none. Everything they’ve delivered has been polished, professional, and done to a very high standard. …
With our partner n.vision on the Business Central side and our engineers on the store, under one point of contact.
Send us the store address. A senior engineer reads its release, support status, PHP, headers, hosting and any sign of a hijack.
Within two working daysWe read the store and your Business Central setup, including customisations, and write down each flow: records, fields, direction, record of truth, frequency.
Before anything is builtThe integration is built against a Business Central sandbox and a staging copy of the store, with your real catalogue, customers and price lists.
Most of the projectOrders, stock and prices flow in parallel with what you do today while your team checks both agree. Mismatches are found here, not in the ledger.
Before go-liveEnabled at a quiet time with a way back. Queues, failures and timings monitored closely in the first weeks, then supported month to month.
Go-live and afterThe usual shape of a Magento and Business Central integration. Your scope may add a flow, drop one or change a direction; this is where the conversation starts.
Sales orders with lines, shipping, payment and promotions, created in Business Central as they are placed.
Available quantity per item and location, back to the store on the agreed schedule.
Base prices, customer-specific and group pricing from Business Central price lists.
New accounts and address changes kept in step, with the system of record agreed per field.
Posted invoices and credit notes against the order, available to the customer in their account.
Despatch confirmation and tracking back to the order, so the customer is told without anyone re-keying.
We price the work, not the clock.
The number of flows, the customisations on each side and the volumes decide the work, so we examine the store and your Business Central setup first and then give you a field-by-field scope and a written estimate. Support and later changes can be ad hoc, itemised on a monthly invoice, or part of a retainer.
Decades of collective experience across Magento 1, Magento 2, Adobe Commerce, Hyvä and Shopify. Very little about your store will be new to us.
You deal directly with the founder. No juniors learning on your store and no account managers between you and the people doing the work.
Small stores and large ones, described in their owners' words. The reviews are quoted on this site word for word.
It works with Magento Open Source, Adobe Commerce and Mage-OS. The integration talks to the Magento APIs that all three share, so the edition you run decides nothing about the connection. The frontend does not matter either: Hyvä and Luma stores connect the same way.
Usually orders go from the store into Business Central, while stock, prices, invoices and shipments come back to the store. Customers can move either way, depending on where you create them. Each flow is agreed with you field by field before anything is built, and the table on this page shows the usual shape.
As often as your stock movements need. The frequency is set per flow during scoping: stock and orders usually update far more often than prices, and a seasonal store may want a different schedule in peak than in January. We recommend a schedule once we have seen your warehouse and Business Central setup.
It is held, logged and visible, and an engineer is alerted. A failed order is never lost silently: it sits in a queue with the reason, is retried where the fault is transient, and is raised with you where it is a data problem on one side or the other. A monthly report says what failed and why.
Us. We scope, build and support the integration with our partner n.vision, who specialise in Business Central, and you have one point of contact for the whole of it: the store, the connection and the questions in between. Your Business Central partner, if you have one, is welcome in the conversation.
Usually not, but it is the first thing we look at. Custom fields, posting groups, dimensions and number series all affect the mapping, so scoping reads your Business Central setup as carefully as it reads the store, and the field-by-field plan reflects what you actually have.
It is priced as a project once we have examined both systems, because the number of flows, the customisations on each side and the volumes decide the work. You get a field-by-field scope and a written estimate before anything is built, and payment is usually spread across the project.
Yes. We have connected Magento stores to Orderwise, SAP, Sage and other systems. This page is about Business Central because we deliver it with a specialist partner; for anything else, see Magento development.
Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.
What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.