Narvar
Narvar integration

Narvar in Polar: what happens after checkout, priced.

The order does not end at checkout. Returns, claims and protection all move money, and they move it after the revenue has already been booked. Bring Narvar into Polar and the post-purchase line lands on the same P&L as the sale, so margin reflects the order that actually stuck.

/

The order that stuck, not the one that shipped.

Returns, refunds, claims and their real cost from Narvar, matched back to the Shopify orders that produced them, so contribution margin is computed on the revenue you actually kept.
Returns
"What actually came back?"
Returned orders and refunded value matched to the sale that produced them.
matched to the order
Cost of the return
"A refund isn't the whole cost."
Return shipping, handling and unsellable stock counted alongside the refund.
beyond the refund
By SKU & reason
"Which products, and why?"
Return rate per product and per reason, so the cause is visible.
per SKU · reason
Margin after returns
"What did I keep?"
Contribution margin computed on the orders that stuck, not the ones that shipped.
on what stuck
Repeat behaviour
"Do they come back after?"
Whether a return ends the relationship or not, read against repeat rate.
return vs repeat
One P&L
"Post-purchase is a silo."
Return cost next to cost of goods, freight and ad spend on one statement.
in the P&L
Setup Guide

How to Connect Narvar to Polar.

A Polar account with Shopify connected, admin on your Narvar account, and Polar's AI Data Engineer, which builds the connector from a plain-language request.
Polar

A Polar account with Shopify

A Polar account with Shopify connected. Narvar data only means something read against the orders behind it.

Connect your data →
Narvar

Your Narvar account

Admin access to Narvar, with the reporting that covers the orders and the period you want to bring in.

Open Narvar →

Polar's AI Data Engineer

No native Narvar connector yet? Describe what you need in plain language and the AI Data Engineer reads the Narvar API, writes the connector and pipes it into your warehouse, in minutes.

1

Ask for the connector ~ minutes

Plain language, no code.
Tell Polar's AI Data Engineer what you want from Narvar in plain language. It reads the source documentation, lays out everything the API offers by category, then writes the connector and pipes the data into your warehouse as governed data. No code, and it ships in minutes.
Worth knowing: this also works on connectors you already have. If the Narvar API exposes a field, you can have it, down to a single hidden one the standard connector never pulled.
2

Netted against the order automatic

Off the revenue it belongs to.
Polar matches Narvar activity back to your Shopify orders and takes returns, refunds and claim cost off the revenue that produced them, rather than as a lump at the end of the month.
3

Read it against margin the payoff

Post-purchase, priced.
Return rate and claim cost sit inside contribution margin and net profit, by product and by market, so the SKUs that come back stop hiding behind the ones that do not.
Get started

Count the order that stuck, not the one that shipped.

Bring Narvar in, take the returns and claims off the revenue they belong to, and read margin on what the customer kept.

Side by side

Narvar handles the return. Polar prices it.

Returns, claims and resolutions live in Narvar, away from the revenue they reverse, so margin is calculated on orders that did not all stick. Polar matches them back to the sale and takes the full cost off, not just the refund.
Narvar

Narvar on its ownon its own

Narvar+

Narvar with Polarblended

The refund is the only cost anyone counts.
Refund, return freight, handling and unsellable stock, all on the order.
Return volume sits apart from the revenue it reverses.
Returns netted against the exact order that produced them.
No view of which products or reasons drive the cost.
Return rate by SKU and by reason, against the margin at stake.
Nothing shows whether a returner ever comes back.
Repeat rate and LTV compared for returners and everyone else.
The Gap

The connector is only half of it.

Once Narvar is modelled against your real orders inside Polar, you can use the result wherever you already work. Ask Polar in plain language, pull it live through the Polar MCP, or schedule it into the report your team reads every morning.
Narvar

Narvar

returns, claims, resolutions
Polar

Polar

landed cost, blended margin

Ask Polar

Polar MCP

Scheduled reports

Featured Use Case

What a return really costs.

The refund is the visible part. Freight both ways, handling and unsellable stock are the rest, and Polar puts all of it on the order.
N Margin after returns Illustrative
Metric
This week
WoW
Net revenue
$482,100
+6%
Orders
3,240
+4%
Blended CAC
$38
-9%
New vs repeat
42 / 58
-3pts
Email revenue
$71,400
+12%
Revenue, returns and their cost, margin on what was kept. Illustrative figures.

The full cost

Beyond the refund

A return costs the refund, the freight both ways, the handling and sometimes the unit. Polar counts all of it against the order rather than the month.

Cause, by product

No SQL

Return rate by product and by reason turns a margin leak into a merchandising or sizing decision you can actually act on.

Your Prompt Library

15 prompts a connected Narvar unlocks.

Return cost, return rate by product and reason, and margin computed on what the customer kept.
Type
Audience
15 of 15
Get started · connect once · net of returns

Revenue looked fine until it came back. Polar counts what stuck.

Bring returns, claims and their real cost into Polar and read margin on the orders the customer actually kept.

Phase 1 ~5 minConnect your data in PolarConnect Shopify and your stack. Polar's semantic layer turns it into governed metrics, then wait for the first sync.
Phase 2 ~ minutesBring Narvar inDescribe what you need in plain language; the AI Data Engineer writes the connector and pipes it into your warehouse.
Phase 3 the payoffRead margin after returnsRefunds and return cost taken off the order, inside contribution margin.