What connects, and what each one needs

Sync a Veeqo catalogue, stock quantities and provider costs, and buy supported shipping labels. Saved OmniStock cost overrides still take priority. You can instead use Shopify or CSV for your catalogue; marketplace reporting works independently of a Veeqo connection.

One field: your Veeqo API key.

• Free on every Veeqo plan. Reading stock works on the free plan; editing stock needs Veeqo's paid Inventory plan, and an edit attempt without it says so rather than failing quietly.
• Buying labels needs Purchase Label and the Rate Shopping API enabled on your Veeqo account. If they are not, label buying is switched off with a message instead of erroring.
• Veeqo has no webhooks, so everything is polled, within Veeqo's own rate limit.

Order revenue, referral and fulfilment fees, settlement reports, advertising spend and return requests, through the Selling Partner API. FBA and merchant-fulfilled orders are reported as separate channels.

Choose your supported marketplace, then sign in to Amazon and approve access when OmniStock sign-in is enabled.

• OmniStock must register and enable its application before seller sign-in is available. That setup belongs to the platform operator, not each customer.
• It needs a Professional seller account and three standard roles: Finance and Accounting, Inventory and Order Tracking, and Amazon Fulfillment. None is a restricted role, so there is no PII justification to write.
• We deliberately request no buyer-PII roles. Customer contact details come from your fulfilment platform instead.
• Existing private-app connections keep their original credentials. A successful authorization starts access checks and import; it does not certify complete history.

Gross line-item revenue, per-line order refunds, product data and returns, through the GraphQL Admin API.

Enter your .myshopify.com domain, then sign in to Shopify and approve access when OmniStock sign-in is enabled.

• OmniStock must enable its registered application first. Existing custom-app and token connections remain supported; new customers do not need to create their own developer app for platform sign-in.
• It asks for order history, product data and returns, and no customer-PII scopes.
• Shopify Payments fees are captured from each order's transactions. Fees charged by other payment gateways are not exposed by the API, and the profit report shows them as absent rather than estimating them.

Order totals, final value and fixed fees, advertising spend and returns.

Sign in to eBay and approve access when OmniStock sign-in is enabled.

• OmniStock must enable its registered application and obtain the API access needed for its features. Seller consent alone does not grant an application access to restricted APIs.
• OmniStock manages the application and redirect configuration. Existing connections retain the application that issued their tokens; customer credentials are not silently migrated.
• Per-order earnings breakdowns are available for US, CN and HK sellers paid in USD; fee and payout totals work regardless.
• Refresh tokens last about eighteen months, and are revoked early if you change your eBay password.

Product charges, commission and item fees, and returns.

Sign in to Walmart and approve access when OmniStock sign-in is enabled.

• OmniStock must enable its registered Walmart application first. Platform sign-in currently supports the United States; existing direct API-key connections remain supported.
• Access checks and the first import determine which returns and financial records are available. Approval is not evidence that every historical record has arrived.
• Items fulfilled by Walmart appear as read-only returns: visible, but actioned in Walmart rather than here.

Amazon, Shopify, eBay and Walmart are the four we connect to. Etsy, BigCommerce, Flipkart, Meesho, TikTok Shop and the rest are not connected, and there is no partial version of that: orders from a marketplace we cannot read are absent from the profit report entirely rather than estimated.

So if most of your revenue is on one of those, the report would be missing most of your business while looking complete. Tell us on the form which marketplaces you sell on and we will say plainly whether that works yet.

Platform sign-in currently offers United States, United Kingdom and Japan. Choose the actual marketplace you sell in; a regional API host is not a promise that every country in that region is enabled.

Existing private-app connections retain their configured marketplace ID and regional endpoint. Other marketplaces need a verified configuration before they are offered in platform sign-in.

Every money figure we report is in one currency, the one you tell us you report in. That can be any of the currencies we support, not just dollars — but it has to be one of them, for the whole account.

If a marketplace hands us a figure in some other currency, we refuse it and say so rather than converting it. A converted number at a rate nobody chose looks exactly like a real one and gets acted on; a gap gets questioned. That means a business genuinely trading in two currencies is not something we can report on yet, and we would rather you knew that now.

Sales taxes vary the same way. In the UK and EU, VAT-registered revenue is reported net of VAT. In India, GST is not modelled: revenue is reported excluding whatever GST the marketplace charged, the CGST, SGST and IGST split is not kept apart, and nothing here is a GST filing.

Open Connections inside the product. Marketplace sign-in takes you through access checks and import progress; connections that need credentials offer their own setup and testing controls. If OmniStock's application is not enabled, the platform operator must finish that setup before you can sign in. System health shows recent sync outcomes once connected.