NewPartner Payouts & Commissions: commission calculated, invoice generated, partner paid.See how it works
Use CasesPricing
AIRSTRIDE CAPTURE

You are owed rebate on deals nobody registered

Capture checks every order against every vendor's rules before it ships, registers the ones that qualify, and shows you the money you missed. Find out how much you were owed.

capture.airstride.ai
Capture rateQuarter to date
Capture rate31%of eligible orders registered
Missed rebate€1.42Meligible, never registered
Capture rate by vendorMissed
Vendor A64%€380K
Vendor B41%€291K
Vendor C28%€244K
Vendor D19%€187K
Vendor E11%€166K
1 short

Order #48211 is one licence below the threshold. Adding one qualifies it.

€1 to 2MRebate missed on one vendor, at one reseller, in one year
20,000Order lines modelled in the first analysis, every verdict with a reason
1 weekTo go live: detecting, registering and reconciling your first vendor
0Blocking calls in your order path. Orders fulfil exactly as they do today
The Problem

Rebate is earned in the order and lost in the process

Every deal-registration programme pays for the same thing: register the deal when it qualifies, then do whatever the vendor asks for next. That has to happen on every line. It does not.

Nobody sees it

Orders go through unchecked

Customer-placed, marketplace, or keyed in by a sales person with too many vendors and too many portals. Nobody stops to ask whether the line just qualified, so it is never registered.

Rules drift

Thresholds move every 60 to 90 days

Eligibility depends on SKU, region, segment, quantity and the price list in force that day. The spreadsheet is stale the week it is finished, and the promotion notice sits in a mailbox.

Registered is not paid

A registration is not a rebate

Most vendors add a step after: attach the order reference, file a claim, wait for approval. Miss it and the deal pays nothing. Then the statement arrives as one number, and nobody can reconcile it. Senior people spend weeks on one vendor by hand, and margin that was available on the transaction is never released.

The Product

Four stages, running on every order line

Capture is a plugin for the resale business, not a system to migrate to. It sits beside your marketplace and does the four things a rebate programme demands, continuously.

Stage 1

Detect

Ingest orders and quotes from your marketplace, normalise them into one canonical line, group lines into deals, and test each against the vendor rules in force on the order date. New orders, and historic ones that are still eligible.

OutputEligibility verdict + rebate value + reason code

Stage 2

Register

Assemble the registration and lodge it in the vendor's partner portal under your own scoped service account. Track it to acceptance, chase anything pending, and flag any gap the vendor needs filled before it goes.

OutputSubmitted registration + vendor reference

Stage 3

Follow through

Whatever the vendor requires after registration, Capture does it: attaches the order reference, files the claim where there is one, chases approval, and warns ahead of every deadline. A registered deal is never left to lapse.

OutputRegistration closed out, every deadline met and logged

Stage 4

Reconcile

Load the vendor's rebate statement, match every paid amount back to its registration, and report expected against received with a variance reason on every unmatched line. Finance gets a number it can sign off.

OutputExpected vs received, per vendor, per deal, per quarter

One engine, every vendor. The core engine is built once. Each additional vendor's programme is loaded as configuration, so a new vendor is plugged in within 24 hours, and programmes we already run switch on the day you start.

How it plugs in

Never in the order path

Your order path is built for speed and your customers notice when it slows. Capture is asynchronous by design: every request is acknowledged before any work is done, so no marketplace process ever waits on it and no slowdown on our side can reach your customers.

Most teams go live on a scheduled file feed, because it needs no change to the order path and is the only pattern that also processes historic orders. The API follows once it is running.

  • The minimum integration is two calls and a receiver. Or one file, on a schedule.
  • Verdicts arrive by webhook, or are pulled from an event feed if your security team would rather expose nothing inbound.
  • Every write is idempotent. A retry never creates a duplicate registration.
  • If Capture is unavailable, orders are unaffected and queued work resumes. Vendor windows are measured in days, not seconds.
Batch fileGo-live

Your existing marketplace export to SFTP or S3 on a schedule. No transformation, no change to the application. Backfills every still-eligible historic order on day one.

Recommended first
Async APIPhase 2

Post each order as it lands, get 202 Accepted back immediately, receive the verdict by webhook. Continuous, near real-time coverage.

Weeks 4+
Event feedNo inbound

The same event stream, pulled instead of pushed. Cursor-based, ordered, replayable for 30 days. For security teams that decline a public callback endpoint.

Optional
Quote-time checkOptional

A synchronous verdict in under half a second while someone is still looking at the screen. A quote of 27 seats that becomes 30 is worth more than a correctly registered quote of 27.

Optional
Vendor programmeRulesScopeIn forceStatus
Vendor A / Deal registration2,040 rows2 regions, 3 segments2026-08 to 2026-10Live
Vendor A / Q4 promotion86 rowsEMEA, Commercialfrom 2026-11-01Scheduled
Vendor B / Partner Programme1,320 rowsGlobal, Enterprise2026-09 onwardsLive
Vendor C / Deal registrationencodingEMEA, APACnot yet setOnboarding
Every verdict records the rule version and the clause that decided it.Rule changes: applied, audited, reversible. No release.
Rules are data

The rulebook is versioned, not remembered

Every threshold, rate, product scope and effective date lives in a date-versioned rule store, parsed from the vendor's own published price files as you receive them. Not from someone's recollection of the last promotion email.

Forward vendor promotion notices to a dedicated mailbox and the change is loaded ahead of its effective date. You typically get 30 days' notice; Capture uses it.

  • New vendor: plugged in within 24 hours, not a rebuild.
  • Both rebate bases are valued on every deal, unit rebate and percentage of partner price, so the number is never challenged on method.
  • No line is silently dropped. Unknown SKUs and missing rule versions go to an exception queue with a reason.
Customer proof

€1 to 2 million a year, sitting in one vendor's rebate

A global software reseller, thousands of sellers, more than 8,500 publishers transacted in a half-year, gave us one vendor's order export under NDA. We modelled it against the programme rules.

Twenty thousand order lines. The rebate actually received in the quarter exceeded the maximum achievable from the SKUs visible in the export, which proved the data the reseller held was incomplete, not that the opportunity was small.

Central estimate: €1.2 million a year missed, around €100,000 of earned margin left with the vendor every month, on one vendor, before upsell rebate is counted at all. At a typical 10% resale margin, that is the profit of €12 million in additional sales.

The reseller's own assessment was that the process was messy and that nobody could say how much was being left on the table. The analysis put a number on it, with every verdict explained, in under a week.

~€100kEarned rebate missed per month, on the first vendor analysed
6 weeksModelled payback of the platform fee after go-live, on the data already shared
100%Of eligible deals registered and followed through, once Capture is live
Start here

Find your capture rate before you change anything

The scan runs on historic orders. No integration, nothing touched, nothing paused. You get the rate you have been running at, the rebate that went unregistered, and a range you can put in front of finance.

Send a vendor pack and an order export

Partner emails, price books, criteria documents, transaction history. CSV or PDF.

Find out what rebate you missed

Covered by mutual NDA before anything is shared. Your data stays yours and never appears in anyone else's result.

  • Your capture rate, by vendor, country, channel and product.
  • Missed rebate, shown as a range where a rule had to be inferred rather than read.
  • The ruleset we built, marked by confidence, for you to confirm or correct.
  • A business case in the format finance needs, not a proposal.
Rollout

Live in one week. Then a new vendor every 24 hours.

Start with the vendor you can already prove. Programmes we already run are loaded on day one; every new one is a gap check, then plugged in within 24 hours. The security review runs in parallel, so approval is never the thing you are waiting on.

Day 1

Mobilise

Security assessment started, DPA signed, data feed agreed, vendor portal service account provisioned, sandbox seeded with your own data.

Days 2 to 3

Detect

Full rule set loaded. Every historic order line classified with an auditable reason, agreed against your own view.

Days 4 to 5

Register

Submission service live. First registrations submitted and acknowledged by the vendor, approval gate on if you want it.

Days 6 to 7

Live and reconciling

Historic period reconciled against the statements you already hold, variance explained line by line.

From week 2

A new vendor every 24 hours

Each sequenced on evidence: a short gap check on historic orders sizes the prize, then the programme is plugged in. Vendors already on the engine switch on immediately.

Programmes in scopeVendors already on the engine, day oneYour top 20 by profit, 24 hours eachAny programme with published rules
Security & access

One credential crosses the boundary. Here is exactly how.

Capture never connects to your vendor directly. Price lists and statements reach us from you; registrations are lodged under your own partner account; you sit between us and the vendor at every point.

A dedicated, scoped service account

You provision a separate partner-portal account for automated registration. Not a copy of anyone's login, so no personal access is duplicated and no leaver event breaks the automation.

Attributable in the vendor's own audit trail

Every action appears under that account, distinguishable from human activity. You can see what was submitted and when, from the vendor's side, without asking us.

Revocable in one move

Disable the account and the automation stops. No dependency on Airstride, no notice period, no negotiation.

Nothing inbound required

Outbound HTTPS from you to us. Static egress IPs for allow-listing, optional mutual TLS, and an event feed for teams that will not open a callback endpoint.

Prefer to hold the credentials yourself?

Human-release mode. Capture prepares every registration in full and a named approver releases them in bulk from the console. Detection, valuation, deadline tracking and reconciliation are unchanged. The only difference is who presses submit.

  • TLS 1.2 or above in transit, AES-256 at rest
  • Tenant-isolated, keys managed and rotated in AWS KMS
  • EU data residency available
  • Independent third-party penetration testing
  • Read the full security posture
Commercials

Priced on what we recover

Two parts, both tied to work done and money collected. Nothing recovered, nothing paid on the share.

Part one

Platform fee, per vendor

Covers the build, onboarding, continuous rule maintenance and reconciliation for that programme. The first vendor carries the core engine; every vendor after it runs on the same engine at a lighter fee.

  • Onboarding engineer through go-live; named, dedicated resource on larger engagements
  • Rule changes and promotions loaded ahead of effective date
  • Console, reporting and exception queue included
Part two

A share of additional rebate recovered

Paid only on rebate the vendor actually pays you that you were not collecting before. You keep the large majority. On the first analysis we ran, the modelled recovery repaid the platform fee inside six weeks of go-live.

  • Measured against the reconciled statement, not a model
  • Baseline agreed before go-live
  • Exclusivity terms available for a defined portfolio

Recovered rebate is pure margin. It reduces net cost of sale on every transaction that qualifies, with no change to pricing, volume or headcount. The vendor line itself becomes structurally more profitable to sell.

Questions

Airstride Capture

What reseller and distributor teams ask before they send us an order export.

Talk to us about your vendors

Capture is software for resellers and distributors that checks every order line against every vendor's deal-registration rules, registers the lines that qualify in the vendor's own partner portal, completes whatever step the vendor requires after registration, and reconciles the rebate statement against what was owed. It runs beside your marketplace rather than replacing it.

Airstride Capture

Send us one vendor's export. We will tell you what you missed.

One order export, one vendor, under NDA. You get back a modelled rebate gap with every verdict explained, and a go or no-go number for your exec team. No integration, no commitment.