What MarkHub does
TUNNING GROUP LLC · Features & the Amazon data each one uses
MarkHub is a profit-analytics and listing-management dashboard for Amazon sellers, built by TUNNING GROUP LLC. It is FBM-first. You connect your own Amazon selling account through Amazon's official authorization flow, and MarkHub reads a defined set of your seller data to answer one question on every order: did this make money? — and to help you keep your own listings accurate.
MarkHub is not affiliated with, endorsed by, or sponsored by Amazon. It never sees your Amazon password, and you can revoke its access at any time from Seller Central.
Below is exactly what each part of MarkHub does and which Amazon Selling Partner API data it uses to do it. Every data type maps to a role we request in our Solution Provider Profile, and MarkHub requests nothing beyond what these features need.
Profit analytics (per-order P&L)
For each of your orders, MarkHub breaks the sale into sale price, Amazon referral fee, cost of goods, FBM shipping label, tax and discounts, and shows the net profit you keep. You add your supplier cost once per SKU; every future order is costed automatically. Figures roll up by day, month, supplier or SKU.
Amazon data used: your order headers and order items (SKU, ASIN, quantity, item price, order status) via the Orders API. Amazon referral fees are estimated from Amazon's standard fee rates for each order.
SP-API role: Inventory and Order Tracking.
Buyer data: MarkHub does not store buyer name, street address, phone number, email or payment information. It temporarily holds limited destination location (city and state/region) attached to the order — used only to show you the geographic distribution of your own sales — for up to 30 days, after which that field is automatically deleted. For fulfillment, MarkHub links you to the order inside Seller Central.
Listing and inventory management
See which of your listings are active, out of stock, suppressed or winning the Buy Box, edit your cost inline, and keep your catalogue accurate without leaving the dashboard. You can also create, update or remove your own offers from MarkHub when you explicitly ask it to.
Amazon data used: your own listing items — price, status, quantity — via the Listings Items API (read and, on your explicit action, write); product title, brand and image via the Catalog Items API.
SP-API role: Product Listing.
Bulk ungate checker
Before you buy inventory, check restrictions on many ASINs at once, straight from Amazon's own restriction data for your seller account, so you don't commit money to products you can't list.
Amazon data used: listing eligibility/restrictions for your account via the Listings Restrictions API.
SP-API role: Product Listing.
Pricing & Buy Box analysis
MarkHub reads the competitive/Buy Box price on your listings so your margin analysis reflects the real market, not a guess.
Amazon data used: competitive pricing / Buy Box via the Product Pricing API.
SP-API role: Pricing.
Note on repricing: automatic repricing (writing prices back to Amazon) is offered as a seller-controlled feature; MarkHub only writes a price to a listing on your configured strategy or your explicit action, always within your own account.
P&L reporting & advertising
Daily, month-to-date and month-over-month views of sales, fees, advertising spend and net profit, with a full order-level breakdown behind every figure.
Amazon data used: your order data via the Orders API; advertising spend via the Amazon Ads API (separate from SP-API).
SP-API role: Inventory and Order Tracking.
Account connection & health
MarkHub confirms which marketplaces your account participates in, to validate the connection and scope everything to the right marketplace.
Amazon data used: marketplace participations via the Sellers API.
SP-API role: Selling Partner Insights.
Supplier price & stock monitor (non-Amazon)
You link each SKU to its supplier's product page; MarkHub tracks the supplier's price and availability so you learn your cost changed before your margin disappears. This reads the supplier's own public page and uses no Amazon data.
Roles we request, and why
| SP-API role | What MarkHub uses it for | APIs |
|---|---|---|
| Selling Partner Insights | Validate the connection, identify the seller's marketplaces | Sellers |
| Inventory and Order Tracking | Per-order profit: order status, items, SKU/ASIN, quantity, price | Orders |
| Product Listing | Read and manage the seller's own offers, including seller-controlled price updates; ungate checker; catalog data | Listings Items, Listings Restrictions, Catalog Items |
| Pricing | Read Buy Box and competitive pricing data for margin analysis and repricing decisions | Product Pricing |
MarkHub does not request the roles that carry full buyer personally identifiable information — Direct-to-Consumer Shipping (buyer name and full street address) or Buyer Communication (buyer email) — nor Tax Remittance or Brand Analytics. The limited destination location it holds (city/state, deleted at 30 days) comes from standard order data, not from a PII-bearing role.
Questions about data or access? support@usemarkhub.com · See also our Data & Security and Privacy Policy.