Docs / Install PunchOut
~10 minutes end-to-end · Chrome / Edge / Brave · Business Central SaaS
Zentriq PunchOut has two pieces, one on each side of the wire: a Chrome extension that lives in the buyer's browser, and a small Business Central extension (a .app file) that lives on your BC tenant. They talk to each other through your Microsoft account. This guide walks both installs end-to-end.
You'll need:
Go to app.zentriqsoftware.com and sign in with the same Microsoft account that holds your Business Central licence. Zentriq uses Microsoft as the sole identity provider — there is no password to manage on our side.
On first sign-in you'll be asked to either create an organization or join an existing one. Create one if you're the first person in your company to set Zentriq up; billing and credit balance are scoped to the organization, not to individual users.
Every new organization starts with a handful of trial credits so you can capture a real cart end-to-end before deciding to pay. No credit card required at sign-up.
Cart captures consume credits. Trial credits cover your first few captures; after that, top up with a one-time pack on the pricing page:
All packs are one-time purchases via Stripe. Credits never expire. VAT (Swiss or EU) is added at checkout based on your billing country.
You can skip this step for now and come back to it after capturing your first cart — Stripe checkout is two clicks from the dashboard.
The Zentriq PunchOut Chrome extension is what watches the cart page on Galaxus, Brack, Microspot and friends, and what triggers the capture.
From the dashboard, click Install Chrome extension. You'll be redirected to the Chrome Web Store listing. Click Add to Chrome (or Add to Brave / Get on Edge — same button, different wording). The browser confirms the permissions, the icon appears in your toolbar.
Beta access: while we're finishing the public Chrome Web Store rollout, the listing is unlisted and accessible only via the direct link in your dashboard. The install behaviour is identical — only discovery differs.
Click the Z icon in your toolbar to open the Zentriq popup. The first time it opens, you'll see a 3-slide onboarding ending with Sign in with Microsoft.
Sign in with the same Microsoft account you used in step 1. Microsoft will ask you to consent to two API permissions:
BusinessCentral.ReadWrite.All — so the extension can write your captured cart into your Requisition Worksheet.offline_access — so the extension can refresh its access token automatically and you don't have to sign in again every hour.Click Accept. The popup discovers your BC environments and companies automatically — pick the one you want PunchOut to write into.
This is the second piece of the puzzle. The Chrome extension can only push lines into BC if a small .app extension is installed on your tenant. It exposes a tiny custom API (Item Templates, Requisition Lines, an action to create missing items) that the Chrome side talks to.
Two ways to get the .app — both end up with the same signed file:
Tracks your install on our side so we can help you debug. Signs you in with Microsoft, takes 30 seconds.
Open dashboard →Forward this link to your BC admin. No Zentriq account needed for the download itself — accounts are checked at first capture.
Download .appThe file is ~12 KB and named Zentriq_PunchOut.app. For SHA-256 verification, email support@zentriqsoftware.com — we publish the checksum of the current release out-of-band.
You have two paths — pick whichever your IT team prefers.
Path A — From inside Business Central:
Zentriq_PunchOut.app file, accept the terms, leave the language as English, click Deploy.Path B — From the BC Admin Center (recommended for IT teams managing multiple environments):
A BC tenant can contain several environments (Production, Sandbox, UAT, …). The .app install is per environment — installing on SwissSandbox does not make it available on Production. If you want PunchOut on both, upload the file on both. It's the same .app, so it's a 30-second repeat.
The .app ships with one permission set named Zentriq Punchout. It grants read access to Vendor, Item, Item Reference, Item Templ., Currency, and read-write access to Requisition Line only. Nothing else is touched.
Assign it to every BC user who will trigger captures:
On the BC company itself the user must already have the standard BC permissions for the tables they want to capture into — Zentriq adds on top, it doesn't bypass.
Back in the browser, click the Z icon → Settings. Make sure:
.app in step 5 (e.g. SwissSandbox, Production).Click Save. The popup reloads its status row. If everything matches up, you'll see BC extension: ✅ Installed. If you see ❌ Not installed, double-check that you're pointing the popup at the same environment where you uploaded the .app in step 5.
Open one of the supported e-commerce sites in another tab — try galaxus.ch, brack.ch, or microspot.ch. Add a couple of products to the cart, then go to the cart page.
Open the Zentriq popup. The Cart page status row turns green: 🛒 Cart detected. The Vendor row resolves to ✅ Brack — CHF (or your matched vendor + currency).
Click the big green 🛒 Capture this cart button.
PunchOut uses AI to read any cart page, so most major e-commerce sites work out of the box. Validated for Swiss B2B procurement:
On other sites, give it a try — if the cart page is a normal HTML cart, the extraction works in most cases. If it doesn't, send a sample cart URL to support@zentriqsoftware.com and we'll tune the parser for it.
Three possible causes:
.app to a different environment than the one selected in the popup Settings. Go back to step 5 or change the environment in step 7.The .app is installed on the right environment but your user can't reach its endpoints. Assign the Zentriq Punchout permission set (step 6) and click ⟳ Refresh.
The cart page is on Galaxus but you don't have a vendor card in BC whose name contains “galaxus”. Create one (the popup gives you a direct link), then refresh.
You haven't finished the BC config in popup Settings. Open Settings, pick Environment + Company, save.
The cart is in CHF but your vendor in BC is configured as EUR (or vice-versa). Either change the vendor's currency in BC, or buy from the vendor's currency-matched store. No credit is consumed when the mismatch is detected pre-capture.
Rare — happens when the BC PATCH call succeeds on the create step but fails on the price update. Zentriq surfaces this as a “N line(s) created without price — verify in BC” warning in the modal. Open the line in BC and fill the unit cost manually.
Zentriq PunchOut and the Zentriq Agent are two separate products. PunchOut runs on one-time credit packs for cart captures; the Agent is a per-seat subscription for the in-BC AI chat. Each has its own .app on your tenant, its own permissions, its own price. You can install one without the other, or both side-by-side — they don't conflict.
When you're ready to add the Agent, follow Install Agent.
Need help with any of this? Email support@zentriqsoftware.com — we answer within one business day, in English, French, or German.
Also see: FAQ · Security & compliance · Pricing.