A fitment-aware storefront on your ERP: make, model, year and engine narrow the catalogue to parts that actually fit, priced from stock in the customer’s own currency.
wrong-part return rate after fitment search went live
Make, model, year, engine. Four taps and the catalogue is no longer 18,000 parts — it is the parts that fit the truck in the workshop bay.
OE code, aftermarket number, VIN or “front brake pads” all land on the same part — including the number that superseded the one they typed.
Everything outside the fitment set is filtered out, not greyed out. The wrong part is not a click away, so it does not end up in the box.
Trade accounts see contract pricing, slab discount and their currency. Retail sees retail. Neither has to ring the counter to find out.
What Riyadh can ship today, what Jeddah holds, and the lead time on anything backordered. No silent substitutions, no discovering it at dispatch.
Trade orders draw on account credit and terms; retail pays by card. Either way the order writes into Business Central with the right customer and tax treatment.
Bin locations, quantities and branch splits come off the same order. A part sourced from another branch is transferred, not cancelled.
The customer sees what shipped, what is following and when. Split deliveries are visible upfront instead of arriving as a surprise short box.
Raised against the original line with a reason code — wrong part, core exchange, warranty. Approved returns post a credit note without anyone rekeying it.
Fitment search moved the wrong-part problem upstream: fewer returns, fewer credit notes, and a counter team answering questions worth their time.
From the first vehicle lookup to the return that never happens.
Make, model, year, engine and variant filter the catalogue to parts that fit — with OE and aftermarket cross-references resolved behind the scenes.
Customer-specific pricing, trade discounts and currency come from Business Central, so the web price is the real price.
Availability shows per branch with lead times on backorder, so a Riyadh customer is not sold a part sitting in Jeddah without being told.
Workshops sign in to their account terms and credit; walk-up customers check out on card. One catalogue, two experiences.
Return requests, core exchange and warranty claims are raised against the original order line, with credit notes posting automatically.
OE number, aftermarket code, VIN or plain description all resolve to the same part, including supersessions and discontinued equivalents.
Your own fitment tables, a commercial catalogue such as TecDoc, or both. We map whatever you have to the vehicle tree and flag SKUs with no fitment coverage so the gaps are visible.
Yes. Signed-in trade accounts get their own price list, discount slab, credit limit and terms, all resolved from Business Central at page load.
Supersession chains resolve to the current part, with the old numbers still searchable. Customers searching a discontinued code land on what replaces it.
Per branch, from your ERP. Where a part is out of stock, the storefront shows the lead time rather than hiding the SKU.
Raised against the order line, with reason codes for wrong part, core exchange or warranty. Approved returns post a credit note in Business Central.
Twenty-one days with a sample of your own SKUs and fitment data loaded.
Twenty-one days, no card. We set the environment up with your own data structure so the trial is worth running.