Dealer Self-Service Parts Ordering: How to Connect Your Parts Catalog to ERP (and the Platforms That Do It)

VNTANA Blogs Dealer Self-Service Parts Ordering: How to Connect Your Parts Catalog to ERP (and the Platforms That Do It)

Last Updated: October 6, 2026

Dealer parts ordering works when a dealer finds the part visually, sees their own contracted price and real stock, and places the order without phoning anyone. That only happens when the catalog reads live from the ERP.

Three integration patterns make it work: direct API, punchout and scheduled file exchange, with middleware able to sit between any of them and the ERP.

This guide explains what data moves between the catalog and the ERP, how each pattern fits, and what to check before you buy.

Key Takeaways (TL;DR)

•

Dealer parts ordering needs four things: correct part identification, the right price for each dealer, real availability and an order that reaches the ERP without rekeying.

•

Data moves both ways. The ERP sends pricing, stock, lead times, order status and documents to the catalog. The catalog sends back a validated order.

•

Match the integration pattern to your order volume and how often prices change. Direct API gives live data, punchout serves dealers who buy through procurement systems and scheduled files suit stable, low-volume lines.

•

Every major ERP has an API route. Each also has a usual challenge, from SAP pricing conditions to Business Central request throttling.

•

Pricing tiers and access control are a common reason rollouts stall, so settle nested dealer groups and SSO before the build starts.

•

Online parts ordering for dealers only holds up when the catalog validates orders, handles supersessions and keeps an audit trail.

Table of Contents

1.

Dealer Parts Ordering: at a Glance

2.

What Dealer Parts Ordering Actually Requires

3.

What Data Moves Between the Catalog and the ERP

4.

Parts Catalog ERP Integration: The Three Patterns

5.

6 Major ERP Systems and What Integration Looks Like for Each

6.

Dealer Parts Ordering Pricing Tiers and Access Control

7.

What to Evaluate in Dealer Parts Ordering Software

8.

Everything You Need to Know About Dealer Parts Ordering

9.

Build a 3D Parts Catalog That Reads From Your ERP

10.

FAQs About Dealer Parts Ordering

Dealer Parts Ordering: at a Glance

Topic

What to know

Goal

A dealer identifies a part, sees their own price and stock, and submits the order with no phone call

Four requirements

Correct part identification, tier-specific price, real availability and order delivery into the ERP

ERP to catalog

Pricing by tier, stock by warehouse, lead times, order totals, status, delivery notes, invoices and shipping documents

Catalog to ERP

The order with validated part numbers, quantities, dealer identity and ship-to

Integration patterns

Direct API, punchout and scheduled file exchange, with middleware able to sit between any of them and the ERP

ERPs covered

SAP, Oracle JD Edwards, Microsoft Dynamics 365 Business Central, Epicor, Infor and Sage X3

Biggest risk

Pricing tiers and access control settled too late

What Dealer Parts Ordering Actually Requires

[IMAGE PLACEHOLDER: image1.jpg]

Dealer parts ordering needs four things, and most catalogs have only the first:

•

The part identified correctly, ideally by clicking it in a 3D parts catalogue

•

The right price for that dealer's tier

•

Real availability, with stock by warehouse

•

The order landing in the ERP without rekeying

A catalog that does the first three and then emails a PDF order form has not solved the problem. The dealer still waits for someone on your team to key the order.

An ERP integrated parts catalog closes that gap with live reads and writes, which makes self-service parts ordering possible.

To see how, the next section shows what data moves between the catalog and the ERP in each direction.

What Data Moves Between the Catalog and the ERP

[IMAGE PLACEHOLDER: image4.jpg]

Plenty of guides say a catalog should integrate with the ERP and stop there. The useful question is which records travel and in which direction.

Dealer parts ordering moves data both ways, and the two directions behave differently.

Direction

Data

What the dealer sees or gets

ERP to catalog

Item pricing by customer tier

Their contracted price on every part

ERP to catalog

Stock levels by warehouse

Which location can ship and how many units

ERP to catalog

Lead time estimates

A delivery window for backordered parts

ERP to catalog

Fulfillment simulation for order totals

Freight, tax and discounts in the cart before submit

ERP to catalog

Order status

Confirmed, picked, shipped or backordered

ERP to catalog

Delivery notes, invoices and shipping documents

Documents inside the dealer's account

Catalog to ERP

The order: validated part numbers and quantities

A clean order line the ERP accepts as is

Catalog to ERP

Dealer identity and ship-to

The order attached to the right account and address

The table shows two flows:

•

The ERP: feeds the catalog price, stock, lead times, order totals, status and documents..

•

The catalog: returns one validated order.

In short, the ERP owns price, stock and orders, while engineering supplies the 3D model and hierarchy from PLM.

Before sending, the catalog checks part numbers, quantities and ship-to. If the ERP goes offline, a well-built catalog shows last known stock with an as-of time and queues orders.

Keeping the above in mind, the next section covers 3 ways to connect the ERP and parts catalog.

Parts Catalog ERP Integration: The Three Patterns

[IMAGE PLACEHOLDER: image3.jpg]

Parts catalog ERP integration comes down to one question: how do the two systems exchange data such as price, stock and orders?

There are 3 major patterns that describe how the exchange can happen:

•

Direct API integration: the catalog asks the ERP for data live.

•

Punchout: a dealer's own procurement system opens your catalog and sends the finished cart back.

•

Scheduled file exchange: data moves between the two systems in batches on a timer.

Each pattern trades implementation effort against how fresh and complete the data is.

Middleware is a translation layer between the two systems. It can support any of the three patterns.

1. Direct API Integration: Real-Time and Highest Fidelity

How it works: The catalog calls the ERP's APIs at the moment the dealer needs something. One call returns the dealer's price, another returns stock by warehouse and a third creates the order.

Because the data is live, the dealer sees what your own counter staff would see.

What it costs you: This requires the most work of the three patterns. Developers map each call to ERP fields, handle authentication, set timeouts and decide what the dealer sees when a call fails.

You also need someone who knows your ERP's pricing logic.

When to choose it: Pick direct API for a large dealer network or contract pricing that changes often. You can also choose it when you promise live stock.

2. Punchout: The Dealer's Procurement System Calls Out to Your Catalog

How it works: A dealer's buyer opens your catalog from a link inside their own procurement system. SAP Ariba, an Epicor-based buying setup or another procurement tool all work the same way.

The buyer picks parts and the cart returns to the procurement system as a structured document, commonly cXML or OCI. The dealer's system then handles approval and the purchase order.

What it costs you: Expect moderate effort. You build a punchout endpoint and session handling while the dealer's team configures their side.

Your catalog still has to pull the right price and stock for that dealer from the ERP during the session, so punchout sits on top of another pattern.

When to choose it: Pick punchout when larger dealers, fleets or government buyers require purchase orders and approval workflows.

At that size, online parts ordering for dealers often starts with a procurement requirement.

3. Scheduled File Exchange: Simplest and Sometimes Correct

How it works: The ERP exports price and stock files to a shared location on a schedule, and the catalog imports them. Orders go back as files on a similar schedule.

What it costs you: This is the lowest effort of the three. Most of the work is field mapping plus a monitor that alerts you when a file fails to arrive.

When to choose it: Pick file exchange when order volume is low and prices change rarely, or when you make no real-time stock promise. In that case, label every stock figure with the time of the last import.

A dealer who sees an as-of time forgives a stale number.

One who sees an unlabeled stale number stops trusting the catalog.

Where Does Middleware Fit?

Middleware is an integration layer that sits between the catalog and one or more ERPs. It translates formats and queues messages, earning its place when you run an older ERP with no modern API or when acquisitions leave you with several ERPs.

Dealers then see one catalog and one set of calls whichever ERP holds their account.

The pattern you pick also has to work with the ERP behind it, so the next section covers how 6 common ERPs connect to a parts catalog.

6 Major ERP Systems and What Integration Looks Like for Each

[IMAGE PLACEHOLDER: image2.jpg]

The integration patterns from the previous section look the same on every ERP. What changes is the connection method and the usual challenge you meet along the way.

Releases vary, so treat the notes below as patterns and check them against your own release.

At VNTANA, we connect the 3D parts catalog to your ERP through open APIs and webhooks. The same approach applies to each of these 6 systems, and we confirm the scope for your ERP and release during a proof of concept.

Here's what each one offers and where teams usually get stuck:

1. SAP

SAP environments typically expose business data through APIs or an integration layer, with the exact method depending on the SAP product and architecture. SAP S/4HANA, for example, exposes OData APIs for business objects such as sales orders and business partners, while older SAP ECC systems often connect through BAPIs and IDocs behind an integration layer.

The common challenge here is customization. Pricing procedures, customer hierarchies, availability logic and order validation may differ significantly from a default SAP setup.

The catalog therefore needs to connect to the manufacturer's actual business rules rather than assume one standard workflow.

2. Oracle JD Edwards

Oracle JD Edwards EnterpriseOne can expose ERP workflows through AIS Server and Orchestrator REST endpoints. That allows an external parts catalog to call defined orchestrations for activities such as retrieving data or creating transactions.

The key is knowing what normally happens around an order inside JD Edwards.

If the manufacturer's internal process performs additional validation, pricing checks or downstream actions, the catalog needs to trigger that logic rather than only create a record.

3. Microsoft Dynamics 365 Business Central

Business Central provides REST APIs for exchanging data with external applications and also supports custom APIs where standard entities do not expose everything the catalog needs.

The integration can therefore be relatively direct until important dealer information lives inside extensions or custom fields.

Pricing rules, account structures or part attributes added specifically for the manufacturer may require custom API objects before they can be used in the ordering workflow.

Cloud environments also limit request rates and return an HTTP 429 error when a client exceeds them, so the catalog needs caching and retry logic.

4. Epicor

Epicor Kinetic exposes business services through its REST API, including access to business objects, queries, functions and ERP processes.

The challenge here is less about whether Epicor can connect and more about choosing the correct business service for each transaction.

An external catalog should follow the same approved ERP logic used internally for pricing, validation and order creation rather than bypassing those rules through direct database writes.

5. Infor

Infor environments commonly use the ION API Gateway in Infor OS as the integration layer between external applications and Infor services.

Products such as Infor LN also provide REST APIs for machine-to-machine communication. Infor, however, covers several ERP products and deployment models.

Before designing the catalog connection, manufacturers need to establish exactly which application owns part data, customer pricing, inventory and order processing.

The integration should follow those system boundaries rather than treating "Infor" as one uniform ERP.

6. Sage X3

Sage X3 provides web-service and API options that external applications can use to read information and create transactions.

For a dealer parts ordering workflow, the main challenge is preserving the business logic that already sits around those records.

Pricing, stock checks, account validation and order controls must behave the same whether an order comes from the dealer catalog or an internal Sage X3 screen.

Dealer Parts Ordering Pricing Tiers and Access Control

Pricing tiers and access control are where many rollouts get stuck. Dealers, distributors, direct customers and internal service teams all log in to the same catalog.

Each group sees different prices and sometimes different parts.

That logic has to exist before the first dealer logs in. Add it after the catalog is built and testing tends to expose a dealer seeing another tier's price or a part meant for someone else. The team then has to go back and rework the rules.

The table below shows how those groups usually differ:

Role

Typical price

Typical part visibility

Dealer

Contracted dealer-tier price

Parts for machines in their territory or brand line

Distributor

Distributor discount schedule

Full catalog with a wider stock view

Direct customer

List or contract price

Customer-facing parts only

Internal service

Cost or transfer price

Everything, including engineering-only items

Each row is a different permission set.

The catalog has to know which row a person belongs to the moment they log in, then show the right price and the right parts for that row.

Three controls handle this, and each builds on the one before it:

•

Role-based permissions: A role defines what a person can see and do in the catalog: view prices, build a cart, submit an order or approve one. Each role is tied to an account in the ERP, so the price a user sees always comes from that account's tier.

•

Nested dealer groups: These cover dealers with more than one location. Take a dealer principal who owns twelve locations. The parent group holds the contract price, and each location has its own ship-to address and counter staff. Once that hierarchy is modeled, the principal sees all twelve locations and a consolidated order history. A counter employee sees only their own cart and ship-to.

•

Single sign-on (SSO): Dealer staff log in with their own company credentials. Access then ends when an employee's company account does, so you do not manage a separate user list for every dealer. VNTANA supports SSO with group-level capability control, which lets you decide what each group can do.

Access control also covers how much of the product a dealer sees.

At VNTANA, our platform strips proprietary geometry and metadata automatically before content reaches external audiences, so no engineer has to act as a gatekeeper.

Stripping controls what leaves your systems, and SSO with group-level capability control limits what each user can do.

Define who sees what before finalizing the catalog design. At login, the catalog must first identify the user's role and dealer account, before applying the right price, stock, documents and actions.

We recommend applying the same roles in your dealer portal software too for consistent pricing.

With these rules set, the next section shows how to test whether a vendor enforces them.

What to Evaluate in Dealer Parts Ordering Software

When comparing interactive parts catalog software for dealer networks, test the complete order flow as well as the viewer features.

Use these questions during evaluation:

•

Integration method: Can the system work with REST APIs, middleware, punchout or scheduled data exchange as required by your ERP architecture?

•

Bidirectional data: Can it retrieve live ERP data and send completed transactions back?

•

Dealer pricing depth: Can pricing vary by account, dealer group and location?

•

Authentication and SSO: Can existing identity providers determine who gets access?

•

Role-based permissions: Can different dealer and internal user types perform different actions?

•

Multi-location accounts: Can one dealer organization contain several locations without creating unrelated user structures?

•

Order validation: Are part numbers, quantities, customer records and order rules checked before submission?

•

Supersession handling: Can the system stop or redirect an order when the ERP reports that a selected part has been replaced?

•

Inventory behavior: Is stock real-time, cached or batch-synchronized – and does the interface make that distinction clear?

•

Audit trail: Can the manufacturer trace who selected, changed and submitted an order?

•

Order status: Can dealers return later to see processing and shipping information?

•

Mobile support: Can a technician identify and order a part while standing beside the equipment?

•

Product data handling: Can the system connect visual product structure with BOM and part records so they stay in sync?

•

Security: Can external users access commercial product content without exposing proprietary engineering files?

If part identification is a major source of mistakes, also evaluate how the system handles engineering data.

Traditional electronic parts catalog software may start with drawings and manually prepared illustrations. For complex equipment, using existing CAD structure can remove much of the work required to create and maintain those visuals.

A CAD-based catalog takes its visuals from files engineering already maintains, so a design change does not mean redrawing illustrations. This is where VNTANA fits.

We're a 3D digital asset management system that converts CAD and BOM data into a clickable 3D parts catalog and syncs with the ERP through API.

VNTANA syncs part and BOM data with the ERP through API, so pricing, stock and orders stay in the system that owns them. If you already run an ordering tool or dealer portal, we can sit upstream and feed it from a single source of truth.

This integration keeps pricing, stock and orders in the system that owns them.

The vendor worth choosing should answer "Yes" across most questions on this list and be able to take a dealer from the first click to a confirmed order without a phone call.

Everything You Need to Know About Dealer Parts Ordering

Question

What to know

What does a dealer need to order alone?

Correct part identification, their own price, real stock and an order that reaches the ERP without rekeying

What flows from the ERP to the catalog?

Pricing by tier, stock by warehouse, lead times, order totals, status, delivery notes, invoices and shipping documents

What flows back to the ERP?

The order with validated part numbers, quantities, dealer identity and ship-to

Which integration pattern fits?

Direct API for live data, punchout for procurement-driven dealers and scheduled files for low volume and stable prices

Which ERPs does this apply to?

SAP, Oracle JD Edwards, Business Central, Epicor, Infor and Sage X3

What commonly stalls rollouts?

Pricing tiers, nested dealer groups and access control settled too late

What should the catalog validate?

Part numbers, quantities, ship-to and supersessions before submission

What happens when the ERP is down?

The catalog shows last known stock with an as-of time and queues the order

What should you check for in a vendor?

Integration methods, tier depth, SSO, order validation, supersession handling and audit trail

Build a 3D Parts Catalog That Reads From Your ERP

VNTANA turns the CAD and BOM data you already own into a clickable 3D parts catalog.

A catalog only works for dealers if it loads fast, stays in sync with your ERP and clears your security review.

Based on that, there are 3 things that set us apart:

•

Patented Intelligent Optimization™ makes heavy CAD files web-ready and is easily customizable per client based on their unique needs.

•

ERP syncs via API, so part information stays tied to the system that owns it.

•

Automatic IP stripping, SSO with group-level capability control and SOC2 Type II certification help the catalog clear security review.

Our platform is built for OEMs and aftermarket teams with a dealer network and a parts catalog that still runs on 2D drawings. It also suits teams whose catalog project has stalled on heavy or unsafe-to-share CAD data.

One of our customers, Roeslein & Associates, was able to launch their parts catalog faster and increase replacement part sales using our platform.

See your CAD and BOM data become an ERP-synced, clickable 3D parts catalog that helps dealers find the right part – book a demo with our team now.

FAQs About Dealer Parts Ordering

Can a parts catalog show dealer-specific pricing?

A parts catalog can show dealer-specific pricing when it requests each dealer's contracted price from the ERP at display time. Login or SSO identifies the account and its tier. The catalog stores no prices itself, so a contract change appears on the next page load. Nested dealer groups inherit the parent price unless a location has its own.

What is a punchout catalog?

A punchout catalog is a supplier catalog that opens inside a buyer's procurement system and sends the cart back for approval. The buyer clicks a link in their system, browses your catalog and returns a structured cart, commonly in cXML or OCI. Their system then creates the purchase order. Dealers on SAP Ariba and similar procurement tools often require it.

Does ERP integration require custom development?

ERP integration needs custom development for direct API connections and little or none for scheduled file exchange. File exchange mostly involves field mapping and a schedule. Direct API work means developers map three calls: price, stock and order creation, and handle the errors each can return. Middleware shortens that work when it already connects to your ERP.

Can dealers order from a 3D parts catalog on mobile?

Dealers can order from a 3D parts catalog on mobile when the 3D model is optimized for phone browsers. A technician rotates the assembly, taps the exact part and adds it to the cart. VNTANA's viewer loads 5–10x faster than alternatives and runs on desktop, mobile, tablet and XR headset. Pricing and orders still come from your ERP.

What happens when a part number is superseded mid-order?

When a part number is superseded mid-order, the catalog should swap in the replacement and tell the dealer before checkout. The ERP's supersession record points the old number to the new one. The cart shows the new number with its own price and stock. If the replacement is a kit or depends on serial number, the dealer confirms the choice.

What is an ERP integrated parts catalog?

An ERP integrated parts catalog is a catalog that reads price, stock and order status from the ERP and writes orders back to it. Dealers browse in the catalog and the ERP stays in the system of record. Nobody keeps a second copy of prices or inventory. Orders arrive in the ERP with validated part numbers, so no one rekeys them.

How does a catalog stay in sync with ERP stock levels?

A catalog stays in sync with ERP stock levels through live API calls, webhooks or a scheduled file. Live calls return the current quantity at each page view. Webhooks push a change the moment the ERP records one. A nightly file refreshes once a day, so the catalog should label the figure with an as-of time.

Do dealers actually want self-service parts ordering?

Dealers want self-service parts ordering, and B2B buyer research points the same way. Zendesk and 2MC Global report that 80% of B2B buyers prefer self-serve evaluation and 75% prefer rep-free interactions. Self-service also takes the routine lookups off your parts counter. Staff then spend their time on urgent orders and hard-to-identify parts.

Ashley Crowder

Ashley Crowder, an expert in spatial computing and digital worlds, is the Co-Founder and CEO of VNTANA, an enterprise 3D Product Digital Asset Management system trusted by manufacturers like Doosan Bobcat, Astec Industries and Kohler. VNTANA publishes 3D product content across websites, dealer portals and parts catalogues. She has 14 patents on mixed reality technology and is a part of the Khronos Group to create standards in 3D technology. She oversees VNTANA's partnerships with SynergyXR, Accenture Song and others. Ashley regularly shares her insight on the future of immersive technology at prestigious events including SXSW, AWE, TEDx, the World Economic Forum, TechCrunch AR/VR Sessions, LA Games Conference, Retail Innovation Conference, eCommerce Festival, Digital Summit, Montgomery Summit, and more. She graduated from USC with a bachelors and masters in engineering. She uses her engineering background to guide VNTANA's direction and technology development, so manufacturers can turn the CAD they already own into content that sells.

View all posts | Follow VNTANA on LinkedIn and YouTube

add_filter( 'aioseo_schema_disable', 'aioseo_disable_schema_for_parent_and_children' ); function aioseo_disable_schema_for_parent_and_children( $disabled ) { // Only execute this logic on standard WordPress pages if ( is_page() ) { global $post; $parent_page_id = 26489; // 💡 REPLACE WITH YOUR ACTUAL PARENT PAGE ID // Check if we are viewing the parent page itself if ( is_page( $parent_page_id ) ) { return true; } // Check if the current page has the target parent page as an ancestor $ancestors = get_post_ancestors( $post->ID ); if ( in_array( $parent_page_id, $ancestors ) ) { return true; } } return $disabled; }