Reconcile the Shopify app charges your standard billing view does not explain
Saxum reconstructs the declared billing population, matches it to available platform records and identifies explained, unexplained and customer-actionable differences.
No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.
Current platform boundary
Shopify App Pricing is the default billing path for common app-pricing workflows and automates much of the standard billing lifecycle. Saxum therefore accepts only bounded legacy, migrated or mixed-record exceptions that the platform’s normal views do not resolve.
Why the standard portal or checklist is not enough
Shopify’s newer managed pricing automates much of the standard billing lifecycle. The remaining opportunity is narrower: legacy migrations, external usage records, plan changes, credits or historical periods that do not reconcile cleanly.
Best-fit customer
Shopify app studios and finance teams managing established apps with historical or mixed billing complexity
Problems this product helps control
Shopify app revenue exceptions where Partner events, subscriptions, usage records and payouts do not reconcile through the standard App Pricing or billing views.
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- Internal charge or usage ledger
- Shopify billing and payout exports
- Plan-change and migration dates
- Known credits, reversals and customer exceptions
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Source-to-platform reconciliation
- Unmatched and duplicated-event register
- Timing and plan-change analysis
- Estimated revenue variance
- Root-cause hypotheses labelled by confidence
- Engineering and finance action list
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Define
Lock the period, billing model and authoritative source records.
Reconcile
Match events, amounts, customer identifiers and timing.
Investigate
Classify differences without treating every mismatch as lost revenue.
Close
Deliver an evidence workbook and prioritized fixes.
Explain every movement from subscription event to expected MRR
The platform can poll authorized Partner API data or process imported snapshots, reconstruct subscription state and turn anomalies into owned, reviewable work rather than a one-off spreadsheet.
Canonical event ledger
Normalize installs, subscription changes, cancellations, freezes, charges, earnings and active subscription state into one reviewable timeline.
Daily MRR bridge
Explain expansion, contraction, churn or frozen revenue by shop and compare expected plan economics with observed state.
Exception-to-resolution
Alert on plan mismatches, active-without-charge and charge-without-earning cases; assign owners, retain evidence and track measurable revenue exposure.
Reconcile billing exceptions across an app studio portfolio
Keep each app ledger isolated while reusing event normalization, exception rules and finance review across multiple apps.
Segregated accounts
Each customer, entity or operating unit keeps separate source evidence, mappings, exceptions and outputs.
Reusable controls
Approved mappings and review policy reduce repeat setup without allowing one client's assumptions to leak into another.
Portfolio oversight
Firm teams can see recurring due work, unresolved exceptions and evidence-backed outcomes without flattening client boundaries.
Show the buyer exactly what Saxum proved
The first controlled cycle produces customer-visible proof before the workflow is expanded. Saxum keeps internal completion separate from external/provider acceptance and never turns estimates into verified outcomes.
Source coverage
See which files, mappings and authority sources were used, what was missing and which assumptions remained unresolved.
Exception register
Every blocker has a reason, owner and current state. Unsupported facts remain open instead of disappearing into a generic pass.
Evidence-graded scorecard
Separate Saxum-completed work from provider-final evidence, verified value, source-backed exposure, observed time savings and estimates.
Use this when the cost of an unresolved exception exceeds the cost of review
Saxum is strongest when the workflow repeats, the evidence is fragmented and one preventable mistake can delay revenue, create rework or weaken the customer’s audit trail.
The diagnostic establishes the expected billing model. Connected assurance then runs on schedule and produces clean-cycle receipts or discrepancy worklists.
Request a billing exception review →Shopify Billing Control FAQ
Direct answers on access, responsibility, deliverables and limits.
No. Standard apps using managed pricing may not need it. The service is for demonstrable exceptions or historical complexity.
No. Saxum identifies and documents discrepancies; recovery and platform communication remain with the app developer.
Not necessarily. File-import diagnostics remain available, while recurring assurance uses a customer-authorized Partner API token.
After Partner API onboarding, Saxum collects historical and current billing events on schedule, rebuilds subscription state, reconciles expected charges and earnings, and alerts on economically material exceptions.
No. Timing, credits, plan changes and accounting cutoffs can explain differences.
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 12 August 2026. Re-check before each engagement.
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.
Saxum Control Platform
Run this workflow in the encrypted control room
Schedule or run the engine, apply saved mappings and connectors, assign exceptions, collect evidence, complete Human ReviewPass and publish signed outputs with measurable value reporting.
Open the control roomSee the workflow before you bring customer data
Every executable Saxum product now has a synthetic first-cycle walkthrough. Where a free checker or guide exists, it is linked here too.