Send them a link. They approve read-only access inside their own Amazon or Shopify login, and the numbers arrive here — sales, settlements, inventory — for an agent to work with. They never create an account with us, and we never see their password.
This is the part every other tool gets wrong by asking the merchant to sign up first. The merchant is not your user. They should not have to become one to show you a number.
One click in the portal, against one system, for one client, labelled however you file it. The link carries what it is allowed to ask for — you cannot widen it afterwards, because the scope is a column on the row, not something the page asks for later.
Email, text, in a thread. We do not send it for you: delivering a message to your client on your behalf is not our call to make, and nothing here sends mail.
A page with no login on it, naming your organization, the account they are about to connect, and every kind of data in plain language. Not scope strings. They can close it and nothing happens.
The authorization happens inside Amazon or Shopify, where they already are. We are handed a token for reading, never their credentials, and the link is spent the moment it is used.
You see which account connected, what they granted, and when it was last read. What they agreed to and when is recorded as it happened. If the authorization ever lapses, you get told, with a reconnect link ready to send.
Adding a connector is a few days of work; adding one nobody has thought through produces a consent screen your client cannot read, which is the single thing this whole surface exists to prevent. So every system here carries a capability list someone designed and an honest reason it is not live yet — and none of them can be authorized today.
Units, price realised and returns — the top line, before anyone has interpreted it.
Sales, settlements and inventory for an Amazon seller account.
The adapter is built against Amazon’s sandbox, and CapitalSource is not yet a registered Amazon developer — so no seller can authorize it today.
Orders, payouts and inventory for a Shopify store.
The adapter is not built. Amazon is first in line so the normalized shape is proven against one store before a second one maps into it.
Orders, settlements and inventory for a Walmart Marketplace seller.
The adapter is not built, and CapitalSource is not an approved Walmart solution provider. Walmart also has no consent screen — the seller hands over an API key — so it works differently from the rest of this list.
The statements an underwriter would otherwise wait three weeks for a PDF of.
Profit and loss, balance sheet, ledger and ageing from a company’s books.
The adapter is not built and CapitalSource has no Intuit developer application. Commerce connectors are ahead of accounting in the queue.
Profit and loss, balance sheet, ledger and ageing from a Xero organisation.
The adapter is not built and CapitalSource has no Xero developer application. It follows QuickBooks so the accounting shape is proven against one set of books first.
Processing volume, payouts and chargebacks. The gap between sales and settlement is often the whole story.
Processing volume, payouts and chargebacks from a merchant’s Stripe account.
The adapter is not built. It is a short one to write, but nothing ships ahead of the Amazon authorization path being proven end to end with a real seller.
Processing volume, withdrawals and disputes from a merchant’s PayPal account.
The adapter is not built, and what a third party can be granted on PayPal needs confirming before it is scheduled. It is here because it is the processor a small merchant is most likely to already have.
Stock on hand and what is going out of the door, whichever system runs it.
Inventory, fulfilment and shipments from whichever warehouse system a merchant runs.
The adapter is not built and CapitalSource has no Trackstar account. One connection reaches the 160-odd warehouse systems we would otherwise never write an adapter for, which makes it the highest-leverage entry here rather than the closest.
The one group here that reads your systems rather than your client’s.
Open opportunities and the businesses behind them, from your own CRM.
The adapter is not built. It reads your own CRM rather than a client’s system; agent readiness does not automatically make this connector available.
Bank data, verification, credit bureaux and the rest of the vendor landscape are tracked on Integrations, where every row carries its real status.
Worth as much as the capability list, and harder to say. These are properties of the code, not promises about conduct.
Every connector we ship declares zero write actions. Nothing we run can change an order, a listing, a price, a payout or a ledger entry. Write access is a separate switch that no connector can currently use.
We read totals, settlements and stock levels. We do not request your customers’ names, addresses or contact details, and there is nowhere in our schema to put them. The accounting connectors skip the customer list; the CRM connector skips contacts entirely.
Your client approves the connection inside their own account and removes it there whenever they like. They never create a CapitalSource login, and we never hold their password.
Each call is written to a signed, append-only ledger naming the connection and the operation. What was read, when, and by which agent is a query, not a support ticket.
Every number an underwriter uses today arrives as a PDF someone collected by hand. A connection is what turns a pre-trained agent from something that talks about a deal into something that has read it — the same standard, the same signed output, with the merchant’s own trading history underneath it.
Agents reach a connection through the same signed capability path as everything else, and every call is counted the same way. There is no second ledger and no side door: a read is a capability call, it is recorded, and its output carries a signature you can verify.
Northside Capital would like to read your Amazon seller account
They will not be able to change anything in your account. They will not receive your customers’ names, addresses or contact details. You can remove this at any time from Seller Central.
The wording comes from the connector itself and is shown to your client exactly as it reads here. A scope string on this screen is the difference between informed consent and a shrug.
The framework is live and the Amazon adapter is built against the sandbox. What stands between here and a real merchant is Amazon’s developer review, which is a queue we are in rather than a feature we are writing. Design-partner slots are open now.