ERP and integrations · 10 min · 2026-11-07
Shopify and Primavera: how to map orders, customers, VAT and shipping without errors
There is no app linking Shopify to Primavera. The decisions before connecting: who owns each data, which document to create, customers, VAT and shipping.
Summary
What matters before moving forward.
- We found no Primavera app on the Shopify App Store. Existing integrations are custom built, by partners or internal teams.
- The first decision is not technical: for each data type, product, price, stock, customer and order, which of the two systems is in charge.
- The second decision is fiscal: does the order enter Primavera as a customer order or as an invoice? If Primavera invoices, no other app can invoice the same sale.
- Customers without a tax number, VAT inclusive prices, shipping and discount codes are the four points where integrations usually break. In our experience, discount codes were the hardest.
- A reliable integration has to know how to fail: each order that does not go through lands on a list with the reason, instead of disappearing.
There is no connect button
Unlike some international ERPs, Primavera has no app on the Shopify App Store that installs in minutes. Anyone wanting to connect the two systems relies on partners with their own connectors or on custom development over the Shopify and Primavera APIs.
That is not necessarily bad. Every company uses Primavera differently: series, warehouses, document types, service items, cost centres. A generic connector would need the same configuration. What changes is that mapping decisions must be made by someone who knows both sides.
What follows is the list of those decisions, as we made them in a Shopify to Primavera integration for a large company.
Decision 1: which system owns each data
Products and prices. In most companies using Primavera, the item is created in the ERP, with reference, VAT rate and price. Shopify receives it and adds what belongs to the store: photos, descriptions, collections. The Primavera reference should be the Shopify SKU, because it is the key that links everything.
Stock. If there is a physical shop, a warehouse or other channels, real stock lives in Primavera and Shopify shows a copy. Update frequency defines the risk of selling what does not exist.
Orders and customers. They start in Shopify and flow to Primavera. The question here is whether a customer is created in the ERP for every purchase or whether sales to individuals go to a generic customer.
Writing this table before starting avoids the worst situation: two systems changing the same data, each undoing the other's work.
Decision 2: which document the order creates
The order can enter Primavera as a customer order, invoiced later in the ERP, or directly as an invoice. The choice depends on who handles shipping and when the invoice must be issued.
This decision has a consequence many stores discover late: if Primavera issues the invoice, no invoicing app in Shopify can issue another for the same sale. Two invoice sources are the most common cause of duplicates.
Also remember the legal deadline. When the customer pays at checkout, before delivery, the invoice must be issued on the date payment is received, under article 36 of the Portuguese VAT Code. The integration has to respect that, even if shipping happens days later.
Decision 3: customers and tax numbers
Shopify has no field for the Portuguese tax number (NIF). Most often it comes from Address 2, a cart field or, on Shopify Plus, a checkout field. The integration must clean and validate that value before creating or looking up the customer in Primavera.
For customers without a NIF, the choice is between creating one customer per person or using a final consumer. For customers with a NIF, the lookup key should be the NIF rather than the email, because the same company often buys with different emails.
Also define what happens when billing and shipping addresses differ, and which one goes on the document.
Decision 4: amounts, VAT, shipping and discounts
Shopify sells VAT inclusive and rounds VAT per line. Primavera needs to know whether it receives prices with or without VAT. The rule that works is to fix the total paid for each line and calculate the base from it, so the Primavera document adds up to exactly what the customer paid.
Shipping is its own line, usually a service item in Primavera, and follows the VAT rate of the goods shipped.
Discount codes were the hardest point. Sending the discount as a single negative line leaves VAT wrong in mixed rate orders. The discount has to be read from Shopify line by line, already allocated, and passed with each item.
Decision 5: what to do when it fails
An order with a SKU that does not exist in Primavera, an invalid NIF or an unmapped VAT rate will fail. The question is what happens next.
The right answer is an exceptions list, visible to whoever runs the store, with the order number, the reason and how to fix it. Once the data is fixed, the order goes through again without duplicating.
Add a daily reconciliation: paid orders in Shopify against documents in Primavera. That is what guarantees nothing is lost when a Shopify notification does not arrive, which Shopify's documentation admits can happen.
How Vokzar builds the Primavera integration
We start with a short workshop with your team and accountant to settle the five decisions above and write the field map.
We build the integration on the Shopify and Primavera APIs, with the SKU as key, amounts calculated per line, allocated discounts, validated NIF, an exceptions list and daily reconciliation.
We deliver it with a set of test orders including the hard cases, so any future change is validated before it reaches invoicing.
Related next steps
Next steps.
Proof and validation
- The absence of a Primavera app on the Shopify App Store was checked in November 2026. Some partners offer their own connectors.
- The experience described comes from a Shopify to Primavera mapping done for a large company.
- The invoicing rules summarise articles 36 and 16 of the Portuguese VAT Code and should be confirmed with your accountant.
Official documentation
Validated sources.
Technical strategy should be auditable. These sources link directly to the official documentation behind this guide.
Frequently asked questions
Common questions about this topic.
Is there an app to connect Shopify to Primavera?
We found none on the Shopify App Store. The connection is made with partner connectors or a custom integration over both systems' APIs.
Should the order enter Primavera as an order or as an invoice?
It depends on who ships and when the invoice must be issued. If Primavera issues the invoice, no app in Shopify can invoice the same sale.
Which field should link products between the two systems?
The item reference in Primavera, used as the SKU in Shopify. It is the key that links products, stock and order lines.
What happens to an order that fails in the integration?
It should land on an exceptions list with the reason and go through again once fixed, without duplicating. A daily reconciliation makes sure no paid order is left out.

