Competitor study, for our A2X discussion

How A2X actually works

Real screenshots from A2X's own product, and an honest write-up of the model. I had been designing off a marketing-level read of A2X. This is the real thing, so we can discuss it from fact.

Your correction was right: in A2X, grouping ("revenue by") is a saved setting, not a live toggle. The screenshots below show exactly where and how.
The core model

A2X is settings-first, not dashboard-first

You configure two things once in Settings: how sales are grouped, and which account each Amazon transaction type posts to. Every settlement journal is then shaped by that configuration. Nothing is a live view you toggle per session.

The whole product is: configure the grouping and the account mapping once, and A2X turns each Amazon settlement into a summarized journal that matches how you keep your books. Change the config, and you re-generate ("refresh") the payouts.
Screenshot 1

Grouping is a saved setting

Settings has a "Sales Grouping and Tracking" page. You pick one grouping mode and save it. This is the exact screen behind the "revenue by" question.

A2X Settings, Sales Grouping and Tracking
Settings → Sales Grouping and Tracking. Three saved choices: All sales, Sales by each SKU, or Sales by Product Type. Note A2X's own warning at the top: "Any changes will alter the mapping requirements in the Accounts and Taxes page." Grouping and account mapping are linked config, not a report filter.
Source: A2X Support Center, product-type grouping article
Screenshot 2

Product types are SKU groups, each mapped to accounts

A "product type" is a named group of SKUs you define in Settings. Each one gets its own account mapping. This is how A2X does brand or category splits, all pre-configured.

A2X Settings, Cost of Goods Sold account mapping by product type
Settings → Cost of Goods Sold. Each product / fulfillment type (here Brand-A, Brand-B) maps to an Expense (Debit) and an Asset (Credit) account via a picker. The left nav shows the whole settings model: Product Types, Sales Grouping and Tracking, Cost of Goods Sold, Connections. It also maps to QuickBooks classes if you enable tracking.
Source: A2X Support Center, product-type grouping article
Screenshot 3

The account mapping page, and where missing mappings get fixed

This is the core chart-of-accounts mapping: every Amazon transaction type maps to one of your GL accounts and a tax rate. On first connect an onboarding questionnaire auto-suggests the whole chart. When something is missing or new, you come here, in Settings, to map it. Exactly the RPP flow you described.

A2X Accounts and Tax mapping table
Settings → Accounts and Taxes. Each transaction type (Adjustments, Advertising, Amazon Delivery and Transport) maps to one of your accounts (Amazon Seller Fees, Amazon Advertising, Amazon FBA Fees) and a tax rate, through pickers. This account has 58 mapping lines; Amazon has 23 default automapping rules. Bulk actions update accounts or tax rates.
Source: A2X Support Center, Navigating the Accounts and Tax Page
Your point, confirmed: missing mappings go to Settings, exactly like RPP. A2X's onboarding auto-map, its per-transaction mapping page, its blank catch-all for new charge types, and its refresh-cache line up one-to-one with RPP's bulk derive, code map, unmapped-code hold, and chart sync. A2X and RPP already converge on the same model. Sticky should adopt it, not reinvent it.
Screenshot 4

What A2X produces

The output is a summarized journal per settlement, split into income, fees, and tax, and it handles Amazon's deferred (accrual) timing carefully.

A2X Amazon Summary Report output
The Amazon Summary Report. Income, Expense, and Tax totals up top, then a line-item split across Settled, Deferred (Accrued / Reversed), and Recognized columns. This is the summarized entry that posts to QuickBooks, shaped by the grouping and mapping you set.
Source: A2X Support Center, Amazon Summary Report article
What this means

The mechanics that matter

Where my mockup was wrong

I drew "Revenue by [Brand] [SKU] [Vendor]" as a live pivot you tap. That is a dashboard idea, not how accounting mapping works. In A2X it is a saved grouping setting that changes the shape of the posted journal, and it can carry into QuickBooks classes. If Sticky offers "revenue by," it should be a configured grouping that drives posting, with a separate reporting view if we want interactivity. Those are two different things and I had merged them.

The other one

ConnectBooks, briefly

Different philosophy. Where A2X is a disciplined ledger tool, ConnectBooks leads with SKU-level profit and inventory, and a one-click export to QuickBooks. It is "profit dashboard first, books second."

"I wait for the settlements to post, usually 4 to 5 days after the Amazon cut-off, and then I login to check. All I have to do is click the green export button and I'm done."
Drew Brassard, CFO, Eagle Peak (ConnectBooks customer testimonial)
DimensionA2XConnectBooks
Core jobSettlement to correct summarized journalSKU-level profit and inventory, synced to books
GroupingSaved setting: all / SKU / product typeProduct-level by default
FeelSober ledger tool for a bookkeeperProfit dashboard for an operator
PostingReview, then send to QuickBooks / XeroOne-click export to QuickBooks / Xero

For our discussion

The real questions A2X raises for Sticky Books:

  1. Should Sticky's grouping be a saved setting that drives posting (A2X's model), a live reporting view (dashboard), or both, clearly separated?
  2. Do we post to QuickBooks classes per group, the way A2X optionally does, so the seller's existing class structure is respected?
  3. Do we match A2X's deferred vs recognized timing so accrual-basis sellers are correct, or start cash-basis and add it later?
  4. A2X stops at "review and export." Our differentiator was posting it for you with verification. Is that the wedge, or do serious bookkeepers actually prefer the manual export A2X and ConnectBooks both keep?
Competitor study by Woz · Sep 1 2026 · screenshots from A2X's public Support Center and ConnectBooks' site · no live account data.