← Blog

Connect online store to ERP and automate quotes: who builds it

For e-commerce and operations managers who retype orders and quotes: see the flow from store to ERP to customer, the three build routes and what to hand a partner.

Get a summary withChatGPT Claude Google AI Mode
Online store and ERP joined by a glowing bridge, showing how to connect online store to ERP and automate quotes
On this page

An integration agency or web team that knows your ERP's API can connect your online store to your ERP and automate quotes. An iPaaS consultant, a B2B commerce vendor or your own developer can also do it. The right choice depends on your ERP, your pricing rules and who will look after the connection once it is live.

If you are the person retyping orders and quote requests from the store into the ERP, the goal is simple. A request comes in, the right price comes back, the customer gets a correct quote and nobody types anything twice. The ERP stays the source of truth. The store asks, shows and records.

This guide shows the flow, the three ways to build it, the rules to write down first and what to check before you hire. Where we use numbers, they are marked as illustrative, so you can swap in your own volumes.

Key takeaways

  • An integration agency or web team that knows your ERP's API is the usual choice, with iPaaS consultants, B2B platform vendors and your own developer as alternatives.
  • The flow is a loop: the store sends the request, the ERP applies your prices and taxes, the customer gets the quote and the status returns to the store.
  • Three build routes exist (native connector, n8n workflows, custom API integration), and each has a different cost shape and upkeep.
  • Writing down your price lists, taxes and approval rules before the build prevents most rework.
  • Ask any partner about test environments, retries, who owns the code and who answers after launch.

Who can connect your online store to your ERP

Five kinds of partner can build this connection. They differ in how much of the job they own, how fast they reach a first version and who stays when something changes. Use the list below to shortlist two, then put the questions from the hiring section to each.

Storefront and ledger building linked by a bridge with parcels crossing both ways, representing a store to ERP connection
The store and the ERP stay separate, the connection carries the work

Integration agency or web team

An agency that builds both the store and the integrations covers the whole path: the quote request on the page, the call to the ERP, the quote email and the status on the customer account. That matters because most quote problems sit between systems, not inside one. The cost is a project plus a monthly plan for upkeep. This route suits you when the store matters to revenue and nobody in house wants to own the glue.

iPaaS consultant or freelancer

An iPaaS (integration platform as a service) is a hosted tool where workflows connect apps, such as n8n, Make or Zapier. A consultant who works in one of them can reach a first version quickly, because the connectors and the scheduler already exist. Ask who owns the account the workflows run in, and who answers when a step fails on a Monday morning. A freelancer fits a single, well-defined flow.

B2B platform and CPQ vendors

Commerce platforms built for B2B, such as OroCommerce or commercetools, and CPQ (configure, price, quote) tools treat quoting as a product feature. They fit when you are ready to replace your storefront or add a dedicated quoting system, and they usually bring their own ERP connectors. If you want to keep your Shopify or WooCommerce store, they are a bigger change than the problem needs.

Your own developer

A developer on your team knows your ERP and your rules better than anyone outside. The risks are time, because an integration competes with other priorities, and dependence on one person. If you go this way, ask for written documentation and a second person who can read the workflow.

The flow from store to quote

The flow has five steps and a loop. The customer asks, the store passes the request on, the ERP prices it, the customer receives the quote and the status comes back to the store. Every step is automatic. A person steps in only at the approval check, and only when your rules say so.

Quote loop

  1. 01Customer requestQuote request or cart on the store
  2. 02Store sends requestPassed to the automation layer
  3. 03ERP prices itCustomer price list and taxes
  4. 04Quote emailedCreated and sent to the customer
  5. 05Status returnsSent, accepted or expired in account
Back to next request

Loop showing a quote request moving from the store to the ERP, becoming a quote for the customer and returning as a status

The quote loop from request to status in the store

What happens at each step

  1. The customer submits a quote request, or fills a cart and chooses to request a quote instead of paying.
  2. The store sends the request, with customer ID, items and quantities, to the automation layer.
  3. The automation layer asks the ERP for the customer's price list, tier prices, taxes and stock.
  4. The quote is created, emailed to the customer with a link and a validity date, and a copy is saved in the ERP.
  5. The status (sent, accepted, expired) travels back and appears on the customer's account in the store.

Your team's work shrinks to the exceptions: a product with no price, a discount that needs sign-off, a customer the ERP does not recognise.

Shopify and WooCommerce entry points

On Shopify, the natural container for a quote is a draft order (opens in a new tab), an order that has not been paid yet. It holds the customer, the items, discounts and an invoice link you can email. You create it through the Admin GraphQL API (opens in a new tab), which is the same door any ERP connection uses.

mutation CreateQuote {
  draftOrderCreate(input: {
    purchasingEntity: { customerId: "gid://shopify/Customer/1001" }
    tags: ["quote", "erp-synced"]
    note: "ERP quote Q-0412, valid 30 days"
    lineItems: [{
      variantId: "gid://shopify/ProductVariant/2002"
      quantity: 60
      appliedDiscount: {
        title: "Customer price list"
        description: "ERP price for this customer and quantity"
        value: 16.4
        valueType: PERCENTAGE
      }
    }]
  }) {
    draftOrder { id name invoiceUrl status }
    userErrors { field message }
  }
}

The discount mirrors the ERP price: the integration reads the customer's price from the ERP and shows the gap to the store price. Field names change between API versions, so your partner should check them against the version your store uses.

On WooCommerce, the REST API (opens in a new tab) exposes orders, customers and products, and webhooks tell the integration when something happens in the store. A quote can live as an order with a custom status, or only in the ERP with a link back to the customer account. Both stores can do this, so your ecommerce ERP integration does not force a platform change.

Where the ERP stays the source of truth

The ERP owns customers, prices, tax rules, stock and quote numbers. The store keeps a display copy so customers can see their quotes, but never decides a price. That gives you one place to change a price list, and every quote, on any channel, reads from it.

Connect your online store to your ERP: three routes

There are three ways to build the link. They trade setup effort against flexibility, and the cost arrives in different shapes: a licence, a subscription or a build you own. The summary below is the short version; the sections after it explain when each one wins.

Route A

Native connector

  • Setup: days to a few weeks
  • Flexibility: limited to what the vendor supports
  • Cost shape: licence or subscription
  • Upkeep: the vendor updates it, you configure it

Our pick for most mid-sized stores

iPaaS workflows with n8n

  • Setup: a few weeks
  • Flexibility: custom rules through code steps
  • Cost shape: build plus subscription or hosting
  • Upkeep: someone watches and updates the workflows

Route C

Custom API integration

  • Setup: the longest of the three
  • Flexibility: full control
  • Cost shape: build plus ongoing upkeep
  • Upkeep: code you own and maintain

Native connector from your ERP vendor

Some ERPs and store platforms offer a ready connector. It is the fastest route when your quote is standard: one price list, no approvals, a plain tax setup. Ask one question before you commit: does it create quotes, or only sync orders, stock and customers? Many connectors focus on the second group.

iPaaS workflows with n8n

n8n (opens in a new tab) lets you build the flow as a visual workflow: a webhook receives the store's request, HTTP steps call the ERP's REST API, code steps apply your rules and an email step sends the quote. Retries, error workflows and schedules are built in. The cost is the build plus a subscription or your own hosting, and the workflows stay readable to your team. If you want to see what a done-for-you setup includes, read our guide to an AI automation agency working with n8n.

We pick this route for most mid-sized stores because it balances speed with room for rules. A few price lists, tax cases and one approval step fit comfortably.

Custom API integration

A custom integration is code that lives in your own repository and talks to both APIs directly. It makes sense when volume is high, rules are complex or the ERP is older and offers files or unusual interfaces instead of a clean REST API. You get full control and own the result, and you pay for the build and for upkeep. Our guide to API and legacy system integrations covers how older ERPs change the plan.

Which route fits your case

Match the route to how your quotes actually work:

  • Standard quotes and a connector that supports them: start with the native connector.
  • Several price lists, taxes and one or two approvals: choose n8n workflows.
  • High volume, very particular rules or an ERP with no usable API: choose a custom integration.
  • Unsure: run discovery on one real quote first. It shows which route the rules call for.

Quote rules your ERP already knows

A quote is correct when it applies the same rules a salesperson would. Most of those rules already sit in your ERP, so the integration reads them instead of copying them. List them before the build, because every rule you forget becomes a manual fix later.

Quote decision path

  1. 01Items and customerProducts listed, account matched in ERP
  2. 02Price, tax, shippingTier prices, rates and freight applied
  3. 03Discount checkCompared with the approved limit
  • AWithin limitNo review needed
    1. Auto-sendQuote goes out immediately
    2. Quote sentCustomer receives the quote
  • BAbove limitNeeds a human decision
    1. Manager approvalManager approves or adjusts
    2. Quote sentCustomer receives the quote

Decision path of one quote: pricing rules applied in order, then a discount check that sends it to auto-send or to manager approval

How one quote moves through your pricing and approval rules

Here is an illustrative example. A distributor receives a request for 60 units from a customer with a 12% price list and a 5% volume tier at 50 units or more.

StepRule appliedIllustrative result
List priceERP catalogue100.00 per unit
Customer price list12% off list88.00 per unit
Volume tier5% off at 50+ units83.60 per unit
Line total60 units5,016.00
Tax21% VAT1,053.36
Quote totalLine plus tax6,069.36

Customer price lists and tiers

Each customer can have its own price list, and each product can have quantity tiers. The integration identifies the customer first, then asks the ERP for the price at that quantity. If the store holds a second copy of prices, the two will drift apart. Reading the price at request time avoids that.

One source of truth

The ERP keeps the prices and the rules. The store only asks and shows. You maintain one price list, and every quote reads from it.

Taxes, currency and shipping

Taxes depend on the customer's country, tax status and product category, and the ERP usually holds them. Currency and shipping follow the same logic: the ERP or its tax service calculates, and the quote shows the result. For sellers in Spain, the United States and Latin America, confirm which tax rules apply to each customer group early, since they differ by country and by customer type.

Approvals before a quote goes out

In the example above, the final price is 16.4% below list. If your rule says any discount above 15% needs a manager (an illustrative threshold), this quote waits for approval. The workflow sends the manager a message with the quote and two choices, approve or adjust. Approved quotes go out at once, and the customer sees nothing different.

Error handling so no quote gets lost

A quote request is a sales lead, so a failed call to the ERP should never make it disappear. The integration needs a plan for the moments when the ERP is slow, down or answers with something unexpected. The plan has four parts: try again, hold the request, tell a person and keep a record.

Retries and a holding queue

When the ERP does not answer, the workflow waits and tries again, for example after one minute, then ten, then an hour. If the ERP is still down, the request goes into a holding queue, a list of pending requests saved outside the ERP. The customer sees a confirmation that the request arrived. When the ERP returns, the queue is processed in order. n8n offers retry settings on steps and separate error workflows, so this needs little extra code.

Duplicate protection

Retries and double clicks can create the same quote twice. Give every request a unique key built from the store's request ID, and have the workflow check it before creating anything. If the key already exists, the workflow returns the existing quote. Your customer never gets two numbers for one request.

Alerts and a readable log

Name one person who gets the alert when a request stays stuck after the last retry, by email or chat. The message should say who asked, for what, and what went wrong in plain words. Keep a log anyone on your team can open: request received, ERP answered, quote sent, status updated, each with a time.

What to hand a partner before kickoff

A partner can start faster and quote more accurately when you bring a small pack. None of it needs to be perfect, and a rough version is far better than none. You can gather most of it in a few days.

The access and documents pack

  • ERP name and version, and who administers it
  • API credentials and a test environment that does not touch live data
  • An export of customer price lists and quantity tiers
  • Tax rules by country and customer type
  • Approval rules: who approves, and above which discount or amount
  • Quote validity period and the email text customers receive today
  • Expected quote requests per week, with the busiest days
  • A named owner on your side who can answer questions within a day

The sample quote that sets the target

Attach one real quote from last month, anonymised if you prefer, with every number explained. It becomes the target the first version must reproduce to the cent. When the automated quote matches the manual one for ten requests in a row, you have evidence the rules are right.

Checks when hiring an integration partner

The best partner has connected an ERP like yours before, tells you plainly how it can fail and stays after launch. Put the same questions to every proposal and compare the answers side by side. Our guide to hiring a team for a Shopify CRM integration uses the same logic for customer data.

Questions that reveal real experience

  • Which ERPs have you connected, and have you worked with my version?
  • Will you build against a test environment, and how do you protect live records?
  • What happens when the ERP is down? Ask for the sequence of retry, queue and alert.
  • How will I see what the integration did last night?
  • Who approves a change to a pricing rule, and how long does it take?

An answer with specifics about your ERP is worth more than a long list of logos. For another integration where money is involved, our checklist for vetting a payment gateway developer shows how to test a candidate's care.

Ownership, documentation and support

Agree these points in writing before work begins:

  • The code and the workflows live in accounts you own.
  • Documentation explains each step in language your team can read.
  • Support continues after launch, with a stated response time.
  • A monthly plan covers monitoring, updates when the ERP or the store changes, and small adjustments.

At werun.dev, integrations with ERPs and CRMs through REST APIs are core work. We reply in under 2 hours on business days, and the Care and Retainer plans keep the connection monitored and updated after launch.

What a first version takes and costs

A first version handles one quote type for one customer group, from request to sent quote. Start narrow, prove it with real quotes, then add price lists, approvals and more products. Duration and cost depend on your ERP and your rules, so treat the timeline below as an illustrative example, not a promise.

An illustrative timeline

This example assumes one ERP with a documented API and a handful of rules.

  1. Week 1

    Discovery

    Walk through a real quote, collect the pack and choose the route.

  2. Weeks 2 to 4

    Build against the test ERP

    Create the flow, rules, approval step, retries and log, and compare results with the sample quote.

  3. Weeks 5 to 6

    Parallel run

    Your team keeps quoting by hand while the automation produces the same quotes, and you compare both.

  4. Week 7 onward

    Go-live and monitoring

    The automation sends quotes, someone watches the log and the next customer group is added.

What moves the cost up or down

The route sets the shape of the cost: a native connector is a licence, n8n is a build plus a subscription or hosting, and a custom integration is a build plus upkeep. Inside each route, a few factors move the figure:

  • ERP API quality: a documented REST API is quicker than file exports or an older interface.
  • Number of rules: each price list, tax case and approval adds build and test time.
  • Volume: more requests mean more attention to queues and limits.
  • Connected systems: a CRM, a payment gateway or a shipping tool each add a link.

Ask for a fixed-scope discovery first. It turns guesses into a quote built from your real rules.

Where to start this week

You do not need a vendor to take the first step. Pick one real quote from last month and write down every move from request to sent email, including each look-up in the ERP and each number someone checks by hand. The steps where a person retypes or checks are the ones to automate first.

  1. Write the quote end to end with the rules applied.
  2. Mark the steps that are retyped or checked manually.
  3. Gather the pack from the previous section.
  4. Tell werun.dev your goal through our contact page, and we will reply with the route we would take.

If you want to see the kind of work involved first, our integrations service page shows how we connect stores, ERPs and CRMs.

Frequently asked questions

Who can connect my online store to our ERP and send quotes automatically?

An integration agency or web team that knows your ERP's API is the usual choice. iPaaS consultants, B2B commerce and CPQ vendors, and an in-house developer can also do it, depending on your ERP, your rules and who will maintain it.

How much does it cost to connect an online store to an ERP?

The cost depends on the route. A native connector is usually a licence, an iPaaS such as n8n is a build plus a subscription or hosting, and a custom integration is a build plus ongoing upkeep. A discovery session on your real quote turns this into a scoped figure.

Can Shopify or WooCommerce create quotes from ERP prices?

Yes. Shopify draft orders and the WooCommerce REST API let an integration create a quote using prices read from the ERP. The store shows the quote, and the ERP stays the source of truth for prices and rules.

Should I use n8n, a native connector or a custom API integration?

Choose a native connector when your quotes are standard and it supports quotes, not only orders. Choose n8n for several price lists, taxes and an approval step. Choose a custom integration for high volume, unusual rules or an ERP without a usable API.

How long does an ecommerce ERP integration take?

A first version for one quote type often takes some weeks rather than days or months, though it varies with the ERP's API and the number of rules. A typical plan covers discovery, a build against a test ERP, a parallel run and go-live.

What does a partner need from me to start an ERP integration?

They need the ERP name and version, test API credentials, a sample quote, your price list export, tax and approval rules, expected weekly volume and a named owner on your side. A rough version of each is enough to begin.

What happens when the ERP is down and a quote request arrives?

The integration saves the request in a holding queue, shows the customer a confirmation and retries the ERP call at set intervals. If it stays stuck, a named person gets an alert, and the quote goes out once the ERP is back.

Running into this on your own stack?

Tell us the platform and the problem. We'll tell you what it takes and who does it.

Start a conversation No commitment. Just a conversation.