USER GUIDEBetterShop Analytics
A complete reference for managing Amazon and TikTok Shop operations — connecting marketplace data, supplier and seller analytics, VAT compliance, AI-assisted insight and advanced reporting in one unified platform.
CHAPTER 1.0Platform Overview
BetterShop is a central command hub for marketplace operations, consolidating supplier and seller data into a real-time view of your business. It connects directly to Amazon's SP-API and to TikTok Shop to deliver insight into sales, costs, inventory, tax and advertising.
The Three Workspaces
The platform is organised into three workspaces. The workspace you are in determines which menus appear in the sidebar — this guide is structured the same way.
Shared Modules
Some areas are available regardless of the active workspace, because they describe the organisation rather than a single sales channel:
| Area | Purpose |
|---|---|
| General | Users, accounts, client focus, marketplaces and the product catalog |
| Monitoring | Background jobs, uploads, task history, alerts and support tickets |
| Analysis | Market analysis and keyword/share-of-voice analysis |
| FBA | Shipments and inbound plans |
| Amazon Advertising | Ads summary, overview, search terms and the advertising audit suite |
| Intelligence | AI Analytics assistant, Knowledge Base and AI Control |
Menus are filtered by permission and by workspace. If a module described in this guide is not visible to you, either your role does not grant access to it or it does not apply to the workspace you are currently in.
CHAPTER 1.1Login & Interface
Accessing the Platform
Once you click Login on the BetterShop homepage, you are redirected to the sign-in page:
https://dashboard.bettershopanalytics.com/login
You can sign in using:
- Credentials provided by the BetterShop team (email + password)
- Google account
- Microsoft account
To switch between Seller and Vendor environments, use the Seller / Vendor toggle at the bottom-left of the sidebar. Then go to Settings to select the target account.
CHAPTER 2.1Users Module
The Users Table lists all users with access to BetterShop Analytics. Administrators can assign Roles and Permissions per user, control which accounts and brands each user can view, and enable two-factor authentication.
New users can only be created via an invitation request sent to the BetterShop team. Use the three-dot menu on each user row to edit roles, accounts, and brand permissions.
CHAPTER 2.2Accounts Module
The Accounts Module is where you manage all Amazon accounts connected to your BetterShop workspace. Each account can be a Seller Central, Vendor Central, or Advertising account.
Account Listing Table
The main view shows all connected accounts with the following columns:
| Column | Description |
|---|---|
| Account Name | Name assigned within the platform |
| Amazon Vendor Account Number | ID of the Amazon Vendor account (if applicable) |
| Account Type | Vendor, Seller, or Advertising |
| Management | Internal, External, or Partner |
| Region | EU, UK, US, etc. |
| Discount % | Vendor only — co-op / contractual discounts for margin calculation |
| Margin BS | BetterShop margin configuration |
| Marketplaces | Linked marketplaces |
| Actions | Edit, delete, configure |
Filters
- Search by Account – Filter by name
- Account Type – Seller / Vendor / Advertising
- Management – Ours / Partner / New
Actions (Three-dot Menu)
- Edit – Opens the side panel to update name, region, discount, margin, marketplaces
- Delete – Permanently removes the account
Manual Sync Jobs (Seller Accounts)
| Action | Description |
|---|---|
| Add Inventory Sync Job | Manual refresh of FBA + FBM inventory |
| Add Sales and Traffic Job | Forces refresh of Business Reports data |
| Settlement Report Sync Job | Imports Settlement reports for fees/financial data |
| Add Tax Sync Job | Manual sync of VAT/tax reports |
| Subscribe | Enables automatic continuous synchronization |
Vendor Accounts
- Start Retail Analytics Job – Manual refresh of Retail Analytics
- Subscribe – Enables automatic Vendor data sync
For the Seller Orders module, you must configure warehouse information via Manage Warehouse Address in the Account actions panel.
CHAPTER 2.3Client Focus
Client Focus is a planning and margin-monitoring workspace built on top of the accounts you manage. It answers a single question: for each client account, what are we actually earning, and how does that compare with what we forecast?
The Four Views
| View | What it shows |
|---|---|
| Client Focus | Current margin position per account — the baseline view |
| Revenue | Forecast revenue per account across the planning horizon |
| Costs | Forecast costs, including the cost lines that erode margin |
| Gross Margin | Forecast gross margin — revenue against costs |
Seller and Vendor Variants
Client Focus exists in a shared form under General → Accounts, and in workspace-specific forms: Seller → Reports → Client Focus and Vendor → Reports → Client Focus. The workspace variants apply the cost and revenue logic of that channel; the shared variant is used for cross-channel planning.
Forecast values entered here become the reference against which actual settlement and invoice data is compared. Keeping them current is what makes the margin views meaningful.
CHAPTER 2.4Marketplaces
The Marketplaces module lists the Amazon marketplaces available to your organisation and the configuration attached to each one — country, currency and the marketplace identifier used when calling Amazon.
Marketplaces underpin a large part of the platform: product listings are mapped per marketplace, prices and fees are marketplace-specific, and most analytics can be filtered or broken down by marketplace.
To see how an individual product is published across marketplaces, use Product Marketplaces.
CHAPTER 2.5Catalog Module
The Catalog Module is the central area for all product-related information. Many BetterShop features (Buy Box, margin calculations, Page Quality, pricing, inventory) depend directly on the data stored here.
The Catalog contains five subsections:
CHAPTER 2.6Products
The Products section is the core catalog area storing all items for connected Amazon accounts. It feeds margin calculations, Buy Box monitoring, Page Quality, pricing, inventory, and brand mapping.
Product Listing Columns
| Column | Description |
|---|---|
| SKU | Imported from Amazon or created manually |
| ASIN | Unique Amazon product identifier |
| Brand | Brand assigned to the product |
| Category | Amazon category mapping |
| Title | Title from Amazon datasets |
| Sub Category | Custom 1/2/3-level subcategory |
| Product Cost | Used for margin and price evaluations |
| Active | Whether the product is tracked by the system |
| Ad Hoc | ERP mapping status against the Zucchetti Ad Hoc catalog, shown on Amazon accounts: Present, Missing or Not checked. A Missing product can be created in Zucchetti directly from the row with the Add button. |
Brand, Category and Sub Category are mapping fields rather than raw Amazon data: they connect the item to BetterShop's own taxonomy and decide how it is grouped in reports. Ad Hoc is the mapping towards the accounting system. All of them can be corrected in bulk through Actions → Export / Upload instead of row by row.
Checking – A recurring job, Zucchetti Catalog Check, runs every day at 04:00 (Europe/Rome) and verifies every active SKU of the account against the Ad Hoc catalog, setting each product to Present or Missing. A SKU that has never been checked stays on Not checked.
Creating – Reserved to Admin users. Select the Missing rows and use Create in Ad Hoc (n) in the toolbar, or the Add button on a single row.
Requirements – The product must be Active, have a SKU, and carry an Italy tax rate (the Amazon.it line in the Expense by Country tab). If any selected product is missing it, the whole request is refused and the offending SKUs are listed. Products already Present are skipped, and a single request cannot mix products from different accounts.
What is sent – Two payloads: the article itself, whose Ad Hoc code is the SKU, and an article key — an EAN-13 alternate code carrying the vendor product identifier plus name and description. BetterShop then re-checks the SKUs, so the column switches to Present without waiting for the nightly job.
The Active Flag
Active = Yes → product is included in Buy Box, pricing tools, margin calculations, and Page Quality checks.
Active = No → product is ignored by all these modules.
Three Ways to Add Products
Manual Creation – Click the Create Product button and fill in details.
Bulk Import / Update – Export the current list (Actions → Export), edit the Excel file, then re-upload (Actions → Upload). Used for mass cost updates, category mapping, brand normalization.
Automatic Ingestion from Amazon – The system syncs daily with Amazon APIs. For Seller: daily sync from the Seller Product Catalog API. For Vendor: products are created from Purchase Orders (last 6 months) and Retail Analytics (last 4 years / 2 years of missing ASINs).
Editing a Product
The three-dot menu on each row gives access to Edit, Delete, and View Details. The edit panel is structured in three tabs:
- Product Tab – Name, account, brand, SKU, ASIN, cost, category, subcategories
- Tech Information Tab – Co-op recharge, chargebacks, dimensions, weight, for margin simulation and Page Quality
- Expense by Country Tab – VAT, margin, expected revenue, shipping cost, retail price per marketplace
CHAPTER 2.7Product Marketplaces
Product Marketplaces is the mapping layer between a product in your catalog and the marketplaces it is listed on. One catalog product typically has several marketplace entries — one per country — each with its own ASIN, price and status.
What You Use It For
Confirm that a product is correctly listed in every marketplace you sell in.
Spot marketplaces where a product exists in the catalog but has no active listing.
Check the marketplace-specific identifiers used by pricing, Buy Box and inventory modules.
Incorrect or missing marketplace mapping is a common root cause of gaps in Buy Box, pricing and margin reports — if a report is missing a country, check the mapping here first.
CHAPTER 2.8Campaigns
The Campaigns section manages the link between Amazon Advertising campaigns and brands defined in the Product Catalog. This mapping is critical because it enables brand-level filtering in Amazon Ads → Advertising Overview.
Why Brand Mapping Matters
If a brand name differs across modules (e.g., BETTERSHOP in Products vs BETTERSHOP 1 in Campaigns), the Advertising Overview will fail to recognize the connection and data will appear under "Non Brand".
Bulk Upload Mapping
Click Upload Bulk in the top-right corner.
Select Download Sample to export a CSV with all campaigns.
Fill in the Sub Brand column using exact brand names from Catalog → Products → Brand.
Save and re-upload the CSV via Upload File.
Daily Synchronization
BetterShop automatically syncs campaigns daily. New campaigns are added automatically. Unmapped campaigns appear under Non Brand in Advertising Overview. First activation fetches the last 6 months of history.
Best Practices
- Use brand names exactly as they appear in the Product Catalog
- Regularly check for unmapped campaigns
- Use Bulk Upload for large-scale updates, manual mapping for individual corrections
- Verify new campaigns after each daily sync
- Also verify the Products table mapping to ensure alignment between Seller/Vendor Analytics and Ads metrics
CHAPTER 2.9Brands
The Brands module is the registry of brands used to group products across the platform. Brand is one of the primary breakdown dimensions: retail analytics, Net PPM, order analytics and advertising reports can all be viewed by brand.
Because brand drives so many reports, products must be attributed to the correct brand in the catalog. Where advertising data uses different brand naming than the catalog, use Ads Brands Mapping to reconcile the two.
User access can be restricted by brand, so a user may see only the subset of products belonging to their assigned brands.
CHAPTER 2.10Categories
Categories in BetterShop are user-defined and used for internal reporting, margin evaluations, price analysis, and product segmentation. They are independent of Amazon categories.
Creating a Category
Click Create Category and configure:
- Name – Internal label
- Commissions – Per marketplace: Referral Fee (%) and Minimal Fee (€)
Categories and commissions are used for Seller profitability calculations. Vendor accounts do not use Amazon referral fees since Amazon acts as the retailer.
CHAPTER 2.11FBA FeesSeller Only
FBA Fees manage the dimensional categories used to calculate Amazon fulfillment costs. These are essential for margin calculations, profitability analysis, and cost simulations.
Fee Listing Columns
| Column | Description |
|---|---|
| Name | Dimensional tier label (e.g., "Standard Envelope") |
| Longest / Median / Shortest Side | Maximum allowed dimensions per side |
| Is Oversize | Whether this tier is classified as oversize |
| Marketplace Fees | Base fee per marketplace, weight threshold, tier type |
BetterShop automatically matches products to fee tiers based on their dimensions and weight stored in the Product tab. If no matching tier is found, FBA cost cannot be calculated.
How a Product Is Matched to a Tier
- Dimensional weight is derived from volume, not from the sum of the sides:
dimensional weight = (longest × median × shortest) ÷ 5000 - Effective weight is the larger of the two:
effective weight = max(actual weight, dimensional weight) - Size tier is the first tier whose limits the product fits on all four constraints — longest, median and shortest side, and weight. Failing any one of them pushes the product into the next tier up.
- Fulfilment fee is then read from that tier's bracket for the destination country. Above the top bracket the fee grows with the excess weight rather than stopping at the last published figure.
Because the effective weight takes whichever is greater, a light product in a large box is charged on its volume. A carton measuring 40 × 30 × 20 cm bills as 4.8 kg however little it actually weighs — which is why accurate dimensions in the Product tab matter as much as accurate weight.
Where a category uses tiered referral fees, each band applies only to the portion of the price that falls inside it, the way income tax brackets work — not the whole price at the top band's rate. The effective percentage you see is the total fee divided by the selling price, so it sits between the bands rather than on one of them.
CHAPTER 3.1Jobs
BetterShop keeps its data current by running scheduled background jobs that pull from Amazon SP-API, TikTok Shop and other connected sources. The Jobs page is where you see what those jobs are doing.
What to Check
| Signal | How to read it |
|---|---|
| Job status | Whether the last run succeeded, failed, or is still in progress |
| Last run time | How fresh the underlying data is — stale reports usually mean a stalled job |
| Account scope | Which account the job ran for; jobs are generally per-account |
Jobs can also be inspected per account from the Accounts module, which opens the job list already filtered to that account.
Bull Board
The Jobs page reports what each job did. Bull Board, alongside it in Monitoring, shows the queues those jobs run on — what is waiting, what is running now and what failed and is being retried. Use the Jobs page for the question "is my data current?", and Bull Board for "is the system actually processing?" — a queue backing up explains a whole set of stale reports at once.
If a report looks empty or out of date, check Jobs before assuming the data is wrong. A failed or delayed ingestion job is the most frequent explanation.
CHAPTER 3.2Category Mappings
Category Mappings transforms Amazon's raw remittance descriptions into structured financial data by defining pattern-matching rules.
Creating a Mapping Rule
Select Type: Invoice (Vendor remittances) or Settlement Report (Seller settlements)
Enter a Pattern — text to find in Amazon's description (e.g., fattura)
Select the Category to assign (INVOICE, CHARGEBACK, RETURN, PROVISION, etc.)
Toggle Is Regex for advanced pattern matching (start/end anchors, format patterns)
Enable Is Active and click Save
Without regex: if the description contains the pattern anywhere, the category is applied. With regex: you can require the pattern to be at the start, end, or in a specific format.
CHAPTER 3.3File Upload
Not every input arrives through an API. The File Upload workflow is the controlled way to bring external files — supplier files, cost files, reconciliation exports — into the platform.
The Workflow
Select the upload type so the platform knows how to interpret the file.
Upload the file and let validation run.
Review the parsed result and confirm, or correct the source file and retry.
Confirmed data is written into the relevant module and becomes visible in its reports.
Logs Upload Files
Every uploaded file is archived and listed under Logs Upload Files, so you can trace which file produced a given set of records and re-download the original.
Because uploaded files change financial reporting, keeping the archive intact matters — it is the evidence for how a number was produced.
CHAPTER 3.4Task History
Task History records the operations the platform has executed on your behalf, so that any change can be traced back to a run.
| Page | Covers |
|---|---|
| Task History | General platform tasks — imports, recalculations, exports |
| Ads Task History | Advertising-specific tasks, kept separate because of their volume and cadence |
Each entry records what ran, when, against which account, and with what outcome. Use it to confirm that an action you triggered actually completed, and to establish the sequence of events when a figure changes unexpectedly.
CHAPTER 3.5Alerts & Email Templates
The alerting system turns platform conditions into outbound notifications, so that problems reach people without anyone having to watch a dashboard.
Email Alerts
Defines which conditions raise an alert, who receives it, and how often. Alerts are the mechanism behind the notification bell in the top bar as well as outbound email.
Email Templates
Defines the content and layout of the messages the platform sends. Separating templates from alert rules means the same message design can serve several triggers, and wording can be updated without touching the rules.
Keep recipient lists tight. Alerts that reach too many people are muted quickly, and a muted alert protects nobody.
CHAPTER 3.6Ticket System
The Ticket System tracks Amazon support cases from inside BetterShop, alongside the data that motivated them. Rather than managing cases in a separate tool, tickets sit next to the invoices, chargebacks and shortages they refer to.
Use it to record the case raised with Amazon, follow its state, and keep the commercial context — the PO, the invoice, the disputed amount — attached to it.
Ticketing is most often used together with Disputes and Chargeback, where an unresolved discrepancy has to be escalated to Amazon.
CHAPTER 4.1Market Analysis
Market Analysis looks outward. Where retail analytics measures your own performance, Market Analysis places it against the wider market so you can tell growth from drift.
Views
| View | Purpose |
|---|---|
| Dashboard | Aggregate market position and headline movement |
| Products | Market view at product level |
| Brands | Brand-level market share and movement |
| Sub Categories | Category-level view, useful for spotting where a category is expanding or contracting |
| Analysis Uploaded | The market datasets that have been loaded, and when |
Market Analysis depends on uploaded market datasets. If a view looks empty or out of date, check Analysis Uploaded to confirm which dataset is currently loaded.
CHAPTER 4.2Keywords Analysis
Keywords Analysis measures visibility: which keywords matter in your categories, and how much of that space you occupy.
Keywords Analysis
The master keyword list — the tracked keyword set that everything else is measured against.
Products Analysis
The product side of the same question: which of your products rank for the tracked keywords, and how that changes over time.
Share of Voice
From a keyword you can open its Share of Voice view, showing how much of the visible result space you hold for that keyword against competitors. Share of voice is the practical measure of whether SEO and advertising work is moving visibility.
Read share of voice together with Search Term and the Advertising Audit — organic visibility and paid coverage explain each other.
CHAPTER 5.1FBA Shipments
The Shipments module tracks stock movements to Amazon fulfilment centres: what was sent, when, and in what state the shipment is.
Shipments can be created for supported couriers directly from the platform, and shipment records link back to the purchase orders and inventory they relate to.
Seller-side shipment tracking also appears under Seller → Inventory → Shipment, and vendor-side dispatch is handled from the PO Manager.
CHAPTER 5.2Inbound Plans
An inbound plan is Amazon's structured description of a delivery into its network: which items, in what quantities, to which destination. The Inbound Plans module lists existing plans and lets you create new ones.
Create the plan and select the products and quantities to send.
Amazon returns the destination and shipment split for the plan.
The resulting shipments are tracked in Shipments.
Inbound Plans is Amazon-specific and is hidden in the TikTok workspace.
CHAPTER 6.1Ads Summary
Ads Summary is the per-account recap of advertising performance — the entry point to the advertising area. It aggregates spend and return across accounts so you can see where advertising is working before descending into campaign detail.
Use Advertising Overview for campaign-level detail, Search Term for query-level detail, and the Advertising Audit when you need to find structural waste.
CHAPTER 6.2Advertising Overview
The Advertising Overview provides a complete analytical dashboard for monitoring Amazon Ads performance across accounts, profiles, and brands.
Access Path
Amazon Ads → Advertising Overview
Available Filters
- Account Selector – One or more Amazon Ads accounts
- Profile (Marketplace) – IT, ES, FR, UAE, etc.
- Brand Selector – Filter by brand (linked to Campaign mapping)
- Date Range – Auto-compares with previous equivalent period
KPI Summary Cards
| KPI | Description |
|---|---|
| Ad Spend | Total advertising investment |
| Ad Revenue | Revenue attributed to ads |
| ACOS | Ad Spend / Ad Revenue |
| ROAS | Return on Ad Spend |
| TACOS | Ad Spend / Total Revenue (organic + paid) |
| Impressions / Clicks | Visibility and traffic metrics |
| CTR / CVR | Click-through and conversion rates |
| Organic Sales | Total Product Sales – Ad Revenue |
Reading the Trend Chart
| Scenario | Interpretation |
|---|---|
| Ad Spend ↑ + Ad Revenue ↑ | Campaigns scaling correctly |
| Ad Spend ↑ + Ad Revenue flat | Potential inefficiency — optimize campaigns |
| Total Sales ↑ + Ad Spend flat | Organic sales improving — strong brand performance |
| TACOS ↓ | Ads becoming more efficient relative to total revenue |
| TACOS ↑ | Ads costing more relative to sales — review budgets/targeting |
Campaign Performance by Type
| Campaign Type | Description |
|---|---|
| SB AUTO / MANUAL | Sponsored Brands – automatic or manual targeting |
| SD AUTO / MANUAL | Sponsored Display campaigns |
| SBV AUTO / MANUAL | Sponsored Brands Video |
CHAPTER 6.3Search Term
The Search Term page provides metrics based on actual customer queries that triggered ads. It supports analysis by brand type, match type, and individual search terms.
Key Sections
- Brand vs Non-Brand – Spend, revenue, and ACOS split between branded and generic terms
- Match Type – Exact, Phrase, Broad performance comparison
- Search Term is NOT Keyword – Terms generating traffic but not actively targeted (harvest opportunities)
- Search Term Summary – Full granular table with campaign, ad group, and match type context
CHAPTER 6.4Advertising Audit
The Advertising Audit is a suite of five diagnostic views. Each one segments advertising spend along a different axis to expose waste, imbalance or missing coverage that a single blended ACOS figure hides.
Campaign Type Segmentation
Splits performance by campaign type — Sponsored Products, Brands, Display — so you can see which formats carry the account and which are underperforming for their share of budget.
Branded vs Non-branded Segmentation
Separates spend on your own brand terms from spend on generic terms. Branded traffic converts well and flatters blended ACOS; separating it reveals the true cost of acquiring new customers.
Match Type Segmentation
Breaks performance down by keyword match type — exact, phrase, broad — showing whether budget is concentrated in controlled, high-intent matching or leaking through broad matching.
Gaps in Keyword Match Type
Finds keywords that are running in one match type but missing in another, so that proven terms are not left without exact-match coverage.
Gaps in Spend Across ASIN
Finds products with uneven advertising coverage — ASINs absorbing spend without return, and ASINs with sales potential receiving none.
Work from the top down: segment first to find where the imbalance is, then use the two gap views to produce a concrete list of keywords and ASINs to change.
CHAPTER 6.5Ads Brands Mapping
Advertising data does not always use the same brand naming as your catalog. Ads Brands Mapping reconciles the two, so advertising spend can be attributed to the right catalog brand.
Unmapped advertising brands produce brand-level reports where spend and sales do not line up. If brand ACOS looks impossible, check this mapping first.
CHAPTER 7.1AI Analytics
AI Analytics is a conversational assistant that answers questions about your own data. Instead of locating the right report and filtering it, you describe what you want to know and the assistant queries the platform for you.
How a Conversation Works
Select the accounts the question applies to, then ask it in plain language.
The assistant plans the query. If the question is ambiguous it asks a clarifying question rather than guessing.
The answer streams back as text, tables and charts.
Useful results can be pinned as dashboards and revisited without re-asking.
Sessions, Files and Feedback
| Feature | Description |
|---|---|
| Sessions | Conversations are kept, so an analysis can be resumed later |
| File attachments | Files can be attached to a conversation and used as context |
| Pinned dashboards | An answer can be saved as a reusable dashboard |
| Feedback | Answers can be rated; ratings feed AI Control |
| Credits | Assistant usage consumes credits, tracked per user |
Agents and Specialists
You are not talking to one model. The assistant is a team: a manager agent receives your question and either answers it or hands it to the specialist that owns that part of the business. Each specialist is restricted to the data and tables of its own domain, which is what keeps answers grounded rather than plausible.
| Agent | Covers |
|---|---|
| BetterShop Seller Manager BetterShop Vendor Manager | The orchestrators. One per workspace; they interpret the question and delegate to the specialist that owns it |
| Seller specialists | Data Analyst, Finance, Inventory and Returns — settlement, margin, stock and return questions on the Seller channel |
| Vendor specialists | Data Analyst, Finance, Inventory, Profitability, Chargeback and Co-op — purchase orders, invoicing, disputes, COOP and Net PPM |
| Ads Specialist | Advertising performance across both workspaces — spend, return and campaign structure |
| Catalog, Suppression and Buy Box Specialists | The catalog-side tools: listing content, suppressed or blocked products, and Buy Box ownership |
| BetterShop Help | Questions about the platform itself rather than your data — where a module is and how it works |
When the manager delegates, the conversation shows which specialist took over. You can also select a specialist directly when you already know the domain — that skips the routing step and narrows the search space.
Plan Mode
For anything beyond a single lookup, the agent first writes an execution plan — a short checklist of the steps it intends to take — and works through it in view, marking each step as it completes. The plan is the reason a long analysis stays auditable: you can see which question is being answered at each step rather than waiting for a block of text.
Some steps pause for you. Where a choice would change the result — a date range, which accounts to include, which of two readings of the question is meant — the agent stops and asks before continuing rather than picking for you.
Access and Credits
Which agents you can reach depends on your role and on the workspace you are in. A user without advertising permissions does not get the Ads Specialist, and vendor specialists do not appear in a Seller-only account. If an agent you expect is missing, it is a permissions question, not a fault.
Credits are counted per user, not per organisation, and every conversation draws on the balance of the person having it. Administrators can review consumption per user from that user's record, which is the place to look when a balance runs down faster than expected.
The assistant answers from your data but is still a generated interpretation of it. For decisions with financial consequence, confirm the figure in the underlying report.
CHAPTER 7.2Knowledge Base
The Knowledge Base is what AI Analytics knows beyond the raw tables. It has two parts.
Documents
Uploaded documents give the assistant business context that is not present in the database — internal definitions, commercial rules, process notes. Documents are listed with their upload state so you can confirm what the assistant is actually working from.
SQL Examples
Curated example queries teach the assistant how questions in your business map onto the data model. Well-chosen examples are the most effective way to improve answer quality for recurring question types. Queries are restricted to an allow-list of tables.
When the assistant repeatedly misunderstands a question, the fix is usually a new SQL example or a clarifying document — not a rephrased prompt.
CHAPTER 7.3AI Control
AI Control is the oversight view for the AI assistant: a dashboard of the feedback users have left on its answers.
| Column | Description |
|---|---|
| User ID / Name / Email | Who left the feedback |
| Rating | Star rating from 1 to 5, filterable |
| Feedback | The free-text comment left with the rating |
Filtering to low ratings and reading the comments is the fastest route to finding where the assistant is failing — and those cases are the input for improving the Knowledge Base.
Per-User Consumption
Feedback is one half of oversight; cost is the other. Each user record carries an AI dashboard showing that user's credit balance, what has been consumed and the cost behind it. Read together with the ratings here, it answers the two questions that matter: whether the assistant is being useful, and what it is costing to be useful.
CHAPTER 8.1Seller AdministrationSELLER
Seller Administration is the settlement workflow: the process that turns Amazon's raw settlement data into a reconciled financial position you can report on.
Admin Manager
The working view. It drives the settlement workflow — selecting the period, running reconciliation, and resolving items that do not balance. This is where the work happens.
Admin Report
The output view. Once a period has been processed in Admin Manager, the report presents the settled result for review and export.
Admin Manager first, Admin Report second. The report reflects whatever state the workflow has reached, so an unfinished workflow produces an incomplete report.
CHAPTER 8.2FBA ReimbursementsSELLER
When Amazon loses or damages inventory inside its network, it owes a reimbursement. This module tracks those cases: what is owed, what has been reimbursed, and what remains open.
Reimbursements are easy to lose track of because they arrive separately from ordinary settlement lines. Reviewing this module on a regular cycle is what turns an entitlement into recovered money.
Amazon applies claim windows. Cases that are not raised within the eligible period cannot be recovered, so ageing items should be prioritised.
CHAPTER 8.3Client FocusSELLER
The seller-side view of Client Focus. It applies seller economics — Amazon fees, FBA costs, advertising and returns — to produce the margin position per client account on the Seller channel.
Compare against Profit & Loss, which derives the realised result from settlement data, while Client Focus carries the planned position.
CHAPTER 8.4Brand PerformanceSELLER
Brand Performance is a daily-metrics dashboard for the Seller channel, tracking how each brand performs over time rather than as a period total.
Because it is daily, it is the right place to see the shape of a change — whether a drop is a single bad day, a step change after a price or listing change, or a gradual slide.
CHAPTER 8.5Seller Tax ReportSeller Only
An API-generated fiscal report extracted directly from Amazon, used for tax validation, VAT reconciliation, accounting audits, and regulatory compliance.
Access: Seller Panel → Reports → Tax → Report
Data Tabs
The report is organized into tabs representing different fiscal views of each transaction: Account Details, Transaction Info, Product Info, Net Amounts, VAT Info, Gross Amounts, Shipping Info, Tax Registration, Invoice Info, Supplier Information.
Shipping Info – Privacy Notice
No private personal data of final consumers is stored or displayed. Only geographical and logistical information required for tax reporting is shown.
Tax Dashboard
The Tax Dashboard aggregates fiscal activity into a central control panel, separating Invoices and Receipts. All data is controlled by a Month / Year selector at the top right.
Dashboard Sections
- Daily Sales Chart – Day-by-day orange (invoices) and yellow (receipts) bars
- Tax Report Summary – Sales and Refunds with Gross, Net, and VAT for both document types
- Revenue by Marketplace – Country-level gross revenue for VAT allocation
- VAT Declarations – Local VAT vs OSS VAT breakdown per country
CHAPTER 8.6Invoices Listing
Detailed list of all fiscal invoices for the selected month, organized via quick-filter tabs:
| Tab | Contents |
|---|---|
| All | All categories combined |
| Italy | VAT jurisdiction = Italy |
| Local EU | Sales within one EU country (DE→DE, FR→FR) |
| Local Ext EU | Local sales outside EU (e.g., GB→GB) |
| Internal EU | Cross-border EU movements (IT→DE, DE→DK, etc.) |
| External EU | Exports outside EU (e.g., GB→JE) |
| B2B | Business customers only |
| B2C | Final consumers only |
| Refund | Returns and credit notes (negative values in red) |
Departure / Arrival = physical movement of goods. Jurisdiction = where VAT is actually applied. These may differ depending on the fiscal regime.
CHAPTER 8.7Receipts, Local VAT & OSS VAT
Receipts
- Regular – Daily receipts per VAT rate (e.g., Italy 22%, 10%, 4%). One row per day with per-rate totals.
- Union OSS – One Stop Shop transactions. One row per day per OSS jurisdiction with Gross, Net, and VAT.
Local VAT
Cards per country (UK, IT, FR, ES, DE…) showing B2C and B2B rows split by VAT rate — Net, Gross, and VAT per rate, with a country total. Used by tax advisors for local VAT returns.
OSS VAT
Cards per OSS country with VAT rates, Net, Gross, and VAT to be paid via OSS. The bridge between Amazon transactions and your quarterly OSS return.
Transfers
Shows inbound/outbound stock movements between FBA countries. Only available after the full monthly Amazon report download. During the month, the tab shows "No Data Found" — this is expected.
CHAPTER 8.8Transfer ReportSELLER
The Transfer Report covers stock movements between marketplaces and fulfilment countries. Cross-border transfers are a VAT event even though no sale occurs, so they must be reported separately from sales.
Transfers are frequently the missing piece in a VAT filing. A country with sales but no corresponding transfer records is worth investigating.
CHAPTER 8.9Settlement
Collects and normalizes all Amazon payment remittances for the Seller account. Settlement data bridges Amazon operational transactions with actual cash movements.
Transactions are grouped into macro categories: Gross Sales Revenue, Sales Taxes, Amazon Commissions and Fees, Adjustments, FBA Reimbursements, Customer Returns/Refunds, Third-Party VAT, Promotions, and more.
Settlement is primarily an internal reconciliation layer. The primary user-facing financial output is Profit & Loss.
CHAPTER 8.10Profit & Loss
Restructures Amazon settlement data into a financial statement view — macro financial groups, monthly comparisons, and clear profitability indicators.
Macro Categories
| Category | Contents |
|---|---|
| Gross Sales Revenue | Principal + Shipping + Gift Wrap (customer-facing revenue) |
| Sales Taxes (Own VAT) | All VAT amounts collected by Amazon |
| Amazon Commissions and Fees | Selling fees, per-item fees, commissions |
| FBA Logistics Costs | Fulfillment, returns, storage, disposal, prep |
| FBA Reimbursements | Inventory reimbursements from Amazon |
| Customer Returns / Refunds | All refund components |
| MF Taxes / Third-party VAT | Marketplace facilitator withheld taxes |
| Sales Discounts / Promotions | Discount and promotion adjustments |
| COGS | Cost of goods sold (order and refund level) |
| EPR Eco-contribution | Environmental contribution charges |
Every macro category can be expanded to reveal micro-level transaction types, and clicking any micro line opens a right-side drawer with full SKU-level transaction detail, search, and export.
CHAPTER 8.11Finances HistorySELLER
Finances History is the archive of financial events retrieved from Amazon over time. Where Settlement and Profit & Loss present a processed position for a period, Finances History keeps the underlying record.
Use it to trace a figure back to its source events, or to investigate a discrepancy between two periods.
CHAPTER 8.12Workflow & Report Export
The Workflow mode generates the Settlement Report as an Excel file (rather than on-screen table) using the same data, calculations, and filters.
Generated Excel Sections
- Orders Report – All order transactions with full column set
- Refunds Report – Refund transactions mirroring the Orders structure
- Invoicing / Billing Report – Pivot by product and country: quantities, net revenue, average price
- Credit Notes Report – Aggregated credit-related movements
CHAPTER 8.13Inventory Dashboard & OverviewSELLER
Two summary views sit above the detailed inventory listing.
Dashboard
The headline inventory position — stock value, coverage, and the items that need attention now.
Overview
A broader breakdown across products and marketplaces, used to understand distribution of stock rather than individual items.
Both views are entry points: act on what they surface in Inventory Listing and Reorders.
CHAPTER 8.14Seller InventorySeller Only
The Inventory module is built on Amazon Inventory Ledger data. Each row represents a daily snapshot of a specific SKU in a specific Amazon warehouse with a specific disposition (SELLABLE, DEFECTIVE, etc.).
Key Balance Columns
| Column | Description |
|---|---|
| Starting Warehouse Balance | Opening inventory for the day |
| Receipts | Units received into Amazon warehouses |
| Customer Shipments | Units shipped to customers (negative) |
| Customer Returns | Units returned by customers |
| Found / Damaged / Disposed | Inventory events and adjustments |
| Ending Warehouse Balance | Final inventory at end of day |
| Location | Country code of the warehouse (DE, FR, GB…) |
CHAPTER 8.15Reorders
The operational replenishment table consolidating sales velocity, stock levels, in-transit quantities, open reorders, and replenishment suggestions into one view.
Color Code
- 🟧 Orange columns – Units leaving (shipped to customers)
- ⬜ Grey columns – Stock on hand
- 🟩 Green columns – Units entering (POs, returns)
- 🟨 Yellow columns – Calculated indicators (totals, averages, coverage)
Recommendation Logic
The system calculates average sales velocity over 7/14/30/60 days, compares with current stock + transit + open reorders, and outputs a suggested reorder quantity per country. Positive values = reorder suggested; Negative/zero = no reorder needed.
The Calculation, Step by Step
The suggestion is computed per SKU per location, in three steps:
- Average daily consumption — each of the four windows is converted to a daily rate and the four rates are averaged with equal weight:
(units₇ ÷ 7 + units₁₄ ÷ 14 + units₃₀ ÷ 30 + units₆₀ ÷ 60) ÷ 4 - Demand horizon — that daily rate is projected over a fixed 45-day window:
demand = average daily consumption × 45 - Net requirement — what you already have or have ordered is subtracted:
suggestion = demand − open reorders − stock on hand
Averaging four rates rather than taking one long window makes the figure react to a recent change without letting a single unusual week dominate it. The 7-day rate carries the same weight as the 60-day rate, so a genuine acceleration shows up quickly — but only a quarter of the suggestion rests on it.
The 45 days are a fixed demand horizon, not a lead time: supplier or inbound transit time is not part of the formula. If your replenishment takes materially longer than that to arrive, treat the suggestion as a floor and add cover yourself.
CHAPTER 8.16Warehouse Check
Reconciles Amazon inventory accounting data over a selected time range. Cross-checks inventory data against Orders and Refunds from Settlement reports.
When a date range is selected (e.g., 01/01/2025–31/12/2025), the Start Stock is automatically calculated as the ending stock of the day before (31/12/2024).
The Check Total column validates: Calculated End Stock vs Amazon End Stock. If they match → reconciliation is correct. If not → discrepancy detected.
CHAPTER 8.17ShipmentSELLER
The seller shipment view tracks outbound consignments on the Seller channel — what has been dispatched, to which destination, and in what state.
For FBA consignments into Amazon's network, see FBA Shipments and Inbound Plans.
CHAPTER 8.18Inventory & Reordering HistorySELLER
Two historical records support the inventory modules.
| View | Records |
|---|---|
| Inventory History | How stock levels have moved over time |
| Reordering History | Reorder decisions previously taken, and their outcome |
Together they answer the retrospective questions: was this stock-out predictable, and did the last reorder cover the demand it was meant to.
CHAPTER 8.19Warehouse MovementsSELLER
Warehouse Movements exports stock movements in the format required by the Zucchetti accounting system, bridging marketplace operations and the accounting ledger.
This is an integration surface. The export format is dictated by the receiving system, so movements must be complete for the period before exporting.
CHAPTER 8.20Seller Orders (FBM)Seller
Centralizes Amazon Seller FBM orders. Used internally to manage shipping workflows via:
- Asendia app (MyLogsolution) – via Excel upload
- Amazon carrier – sending order info directly to supplier
Each order row shows: Amazon Order ID, Address, Marketplace, Items Shipped, Is Edited, Sent to Supplier, Tracking ID, Total Amount. The Shipments modal shows shipment status, carrier, shipping service, tracking, and packing slip options.
CHAPTER 8.21Buy Box – SellerSeller
Seller Buy Box Logic: Buy Box is WON only if won by the Seller Account's own Seller ID. Amazon winning = LOST for Seller analysis.
The 30-day history chart shows daily Buy Box price with Seller ID resolved to Store Name. Clicking the Seller counter opens an offer comparison panel showing price, shipping, fulfillment type (FBA/MFN), and Prime eligibility.
CHAPTER 8.22Listing Management & AI Optimization
Listing Management is the workspace for the content of your product pages — titles, bullets, descriptions and attributes — across the catalog.
AI Listing Optimization
The AI-assisted counterpart. It proposes improved listing content for a product, which you review before anything is applied. The intent is to remove the blank page, not to publish unreviewed text.
Select the product and the marketplace whose listing you want to improve.
Generate suggestions and compare them against the current content.
Accept, edit, or discard — nothing changes until you approve it.
Generated copy can misstate product facts such as compatibility, materials or dimensions. Check claims against the real product before accepting.
Listing Management and AI Listing Optimization are available in both the Seller and Vendor workspaces.
The AI Listing Optimization Workspace
AI Listing Optimization is its own page in the menu, separate from Listing Management. It is organised as five tabs that follow the life of a listing from source content to approved copy.
| Tab | What it holds |
|---|---|
| Catalog | Listings already in the platform, taken from your Amazon catalog. The usual starting point. |
| Uploaded listing | Listings brought in from an Excel file — for products that are not in the catalog yet. Download the template, fill it, upload it. |
| Optimized listing | The versions the AI has generated, grouped by product, ready to compare against the original. |
| Review | Optimized versions you have marked for review — the queue waiting for a human decision. |
| Approved | Versions that were approved. From here they are exported or sent by email. |
The Workflow
Choose the source – Select the rows to work on in the Catalog tab, or in Uploaded listing if you imported them from Excel.
Review the keywords – Before generating anything, check the keywords the optimization will be built on. You can exclude the ones that do not fit, add manual keywords, and assign each keyword to a group. Competitor ASINs can be attached to a listing so the analysis takes them into account.
Run the optimization – Pick the tone (Professional or Modern & Trendy) and start the job. Generation runs in the background per product, so the page reports progress instead of blocking; results land in the Optimized listing tab.
Compare and select – Read the generated version next to the original. Discard what is not usable, and mark the versions worth keeping for review.
Approve – In the Review tab, approve the versions you accept. They move to the Approved tab.
Deliver – From Approved, export the listings or send them by email to the person who will publish them.
Keyword Groups
Keywords are assigned to three groups, each with a maximum number of entries. The limits keep the generated copy focused instead of stuffing every keyword into the title.
| Group | Maximum | Use |
|---|---|---|
| Primary | 5 | The terms the listing must rank for |
| Secondary | 10 | Supporting terms |
| Long tail | 12 | Specific, lower-volume phrases |
Generated titles are checked against a target of 70–75 characters. A title outside that range is flagged with the exact character count and how far off it is, so you can fix it before approving.
Approval marks the version as accepted inside BetterShop — it does not push anything to Amazon. Approved content leaves the platform as an export or an email, and someone still has to apply it on Amazon.
CHAPTER 8.23Block ProductsVendor
Displays listing/offer issues (blocked listings) extracted from Amazon for Vendor accounts.
Setup Requirements
Go to Accounts → Account Details and enter the Vendor Code for the account.
Go to Jobs → Add Job. Set Queue: catalog-job-queue, Job Name: blocked-products. Submit.
Verify execution in Monitoring → Bull Board (catalog-job-queue → Completed tab).
Return to Vendor → Tools → Block Products and refresh until the table populates.
The Reason field is the key operational element — it explains exactly why an offer/listing is blocked (e.g., profitability reasons, multipack requirements).
CHAPTER 8.24Page Quality
Checks product page content against expected content, focusing on title length, bullet point character limits, and completeness. Navigate via Tools → Quality → Page Quality.
Workflow
Click Manage Product Page Quality and download current Amazon content for the target account.
Click Download Template from Check Product Page Quality, fill in expected content (Title + 5 Bullet Points per ASIN/Marketplace).
Upload the filled template via the CSV upload modal.
Review results: Green = content matches expected. Red = discrepancy detected.
Also Available Under Quality
- Page Variations – Upload Parent ASINs to count and inspect child ASIN variations
- A+ Content – Check A+ Content availability and images per product
- Reviews – Historical review and rating counts
CHAPTER 8.25Page Variations
Page Variations inspects how product variation families — size, colour, format — are structured on Amazon.
Variation structure has direct commercial consequence: a correctly grouped family concentrates reviews and traffic on one page, while a broken family splits them across weaker listings. This view exposes products whose variation relationships are incomplete or wrong.
CHAPTER 8.26A+ Content
A+ Content tracks the enhanced brand content applied to product pages — which products have it, and which are still relying on the basic listing.
Because A+ Content affects conversion, the coverage gap it exposes is a direct list of pages worth improving.
CHAPTER 8.27Product Reviews
The Reviews module collects customer reviews across your catalog so that rating movement can be monitored centrally rather than page by page.
Reviews are an early indicator: a falling rating usually precedes a fall in conversion and Buy Box share, and negative review themes frequently identify a listing or quality problem before it appears in returns data.
Read alongside Returns — review themes and return reasons often describe the same underlying issue.
CHAPTER 8.28Pricing Analytics – SellerSeller
Similar structure to Vendor Pricing Analytics but uses Seller-specific data sources: FBA fee tiers from Catalog, Amazon referral fees from Categories, and Catalog-defined costs.
The Price Optimization action calculates the minimum consumer price to cover product cost + Amazon fees + FBA fees + VAT + target margin. Results are displayed without overwriting existing data.
Blue metric values link directly to the Product edit page for quick updates to dimensions, costs, and expense-by-country configuration.
How Gross Profit Is Built
Every row derives from the consumer price. The order of operations matters, because VAT is removed before costs and fees are subtracted:
- Net the price of VAT — the consumer price is divided by (1 + VAT rate), giving the amount you actually receive.
- Fees on the gross price — the Amazon referral fee and the BetterShop fee are each a percentage of the consumer price, not the net one, and the FBA fee is added as a fixed amount:
total fees = consumer price × referral % + consumer price × BS % + FBA fee - Gross profit — product cost and those fees come off the VAT-free amount:
gross profit = (consumer price ÷ (1 + VAT)) − product cost − total fees
The Revenue column is product cost + gross profit, and Extra is that figure minus product cost — so Extra equals gross profit. They are two views of one number, kept apart because Revenue is what the margin percentage is taken against.
Because referral and BetterShop fees are charged on the VAT-inclusive price while profit is measured on the VAT-free one, the effective fee burden is higher than the headline percentage. In a 22% VAT market a 15% referral fee consumes roughly 18% of what you actually keep.
Pricing Analytics V2
A second, newer entry sits beside this one in the menu. It works on the same pricing model and the same cost inputs, but rebuilds the table on the current grid — faster filtering and sorting on large catalogs, and column settings that persist. Both are available while the rewrite is completed; where the two disagree on a figure, the underlying product cost configuration is the thing to check.
CHAPTER 8.29ReturnsSELLER
The Returns area covers what came back and why, across three views.
| View | Purpose |
|---|---|
| Returns Overview | Return volume and value, with movement over time |
| Products | Returns attributed to individual products |
| Product Returns | Return reasons — the diagnostic view |
Return rate alone only signals that something is wrong. Reasons tell you what: a sizing problem, a misleading listing, a packaging failure or a quality defect each imply a different fix.
Returns Analytics
Focuses exclusively on FBA customer returns. Three sub-sections:
- Returns Overview – Time chart of Ordered Qty, Total Returns, Return Rate %; pie chart by disposition (Customer Damaged, Sellable, Defective); bar chart by reason
- Products (Returns) – Top products by return volume with Return Rate % per SKU/ASIN
- Product Returns – Transaction-level table showing each return reason per product — used for root-cause analysis
CHAPTER 8.30Performance ViewSELLER
Performance View is the current generation of seller performance reporting. The same performance model is presented through four lenses, so a result can be traced from the aggregate down to the item.
| View | Answers |
|---|---|
| Products | Which individual products drive the result |
| Brands | How each brand performs |
| Accounts | How each account performs |
| Sub-categories | How performance distributes across category |
Start at Accounts or Brands to locate the movement, then switch to Products to identify what actually caused it.
CHAPTER 8.31Retail AnalyticsSELLER
Retail Analytics is the seller sell-out reporting suite: what actually sold, broken down along the dimensions of your business.
| View | Purpose |
|---|---|
| Dashboard | Headline sell-out position and trend |
| Products | Product-level sales performance |
| Marketplaces | Performance by marketplace and country |
| Accounts | Performance by account |
| Brands | Performance by brand |
| Sub Categories | Performance by category |
This documents the current Retail Analytics suite. An earlier generation of these pages has been retired from the menu; if you have old bookmarks pointing at them, replace them with the pages listed above.
CHAPTER 9.1Vendor ReportsVendor Only
The Vendor Reports menu is the administrative and financial core for Vendor Central accounts. It includes:
Use the Vendor/Seller toggle at the bottom-left of the sidebar to activate the Vendor panel.
CHAPTER 9.2Administration – Purchase Order Reconciliation
The Administration page consolidates all Purchase Orders and calculates the actual net margin after accounting for discounts, COOP, chargebacks, accepted quantities, and shipping costs.
PO Table Columns
| Column | Description |
|---|---|
| Purchase Order | PO identifier |
| Vendor Code / Brand | Vendor and brand reference |
| Ordered / Accepted Quantity | Volumes ordered vs accepted by Amazon |
| Delivery Window | Shipment period |
| Unit / Total Discount Price | Discounted amounts |
| Product Cost / Total Product Cost | Internal cost values |
| Unit Margin / Total Margin / Margin % | Calculated profitability |
Monthly Margin Summary Chart
Below the PO table, a summary chart shows month-by-month profitability with:
- Margin (purple bars) – Gross margin before shipping costs
- Net Margin (green bars) – Effective profit after shipment costs
- Discount Price (light purple) – Discounted invoice amount after co-op
- Shipment Cost (negative bars) – Monthly shipping expenses
- Margin % (line) – Profitability ratio on right axis
Hover over any bar to see a tooltip with complete monthly values. Use the Year Selector (top-right) to switch financial years.
CHAPTER 9.3Client FocusVENDOR
The vendor-side view of Client Focus, applying vendor economics — purchase order prices, allowances, chargebacks and COOP contributions — to produce the margin position per account on the Vendor channel.
The realised counterpart lives in Account Summary and the invoicing modules.
CHAPTER 9.4Invoice DashboardVENDOR
The Invoice Dashboard is the summary layer above the invoicing detail: total invoiced, total paid, and the outstanding discrepancy across the account.
It exists to answer the first question — how much is unreconciled overall — before you descend into Invoicing to work through individual invoices.
CHAPTER 9.5Invoicing Module
The Invoicing module is the core workspace for monitoring issued invoices, reconciling Amazon payments, identifying discrepancies, and determining which open invoices require accounting action.
Invoice Table Key Columns
| Column | Description |
|---|---|
| Invoice Date / Payment Date | Dates of issuance and payment |
| Invoice Number / PO | Invoice reference and linked Purchase Order |
| Invoice Amount | Total amount billed to Amazon |
| Amount Paid | Amount Amazon has paid so far |
| NC Amount / NC Number | Credit note reference and value |
| Discrepancies ⚠️ | Most important field — unpaid difference (0 = fully reconciled) |
| SC / SC- / SCR / SCRSC | Amazon shortage claim audit workflow stages |
How Amazon Payment Cycles Work
Amazon receives the invoice and may withhold the full amount (shortage claim).
Amazon progressively adds back partial amounts, applies corrections and counter-corrections.
Cycles repeat: payment → retention → correction → retention → correction…
When Amazon stops adjusting, the remaining discrepancy is calculated.
If Discrepancy ≠ 0, the invoice requires action (dispute, credit note, or escalation).
CHAPTER 9.6Payment Cycle
The Payment Cycle provides the most detailed view of how Amazon manages each invoice's payment lifecycle — initial payment, retentions, shortage claims (SC/SCR), adjustments, and final settlement.
Use the search bar to isolate a specific invoice, then expand the row to see the full historical payment breakdown including each SC/SCR event with its amount, description, and date.
Invoice 5371: Amazon initially withholds €8,845 → corrects → re-withholds €8,296 → corrects → finally withholds €8,287 with no further correction → final discrepancy: –€8,287.12
CHAPTER 9.7Recap Costi Extra
Provides a monthly summary of all cost categories extracted from Amazon payment remittances, organized by cost type and month for the full year.
Cost Categories
Chargeback, Invoice, Return, C2FO, Provision, Audit, Coop, PQD, PQV, PPV, DFP/Advertising, AVS, Uncategorized — each shown with monthly totals and a year total.
Used for monthly closure, variance analysis, deduction trend monitoring, and identifying unusual cost peaks.
CHAPTER 9.8Remittance
Remittance exposes every payment event processed by Amazon — the raw remittance rows from which all upstream dashboards and reconciliation tools are built. It is the foundation layer of the entire Vendor reconciliation system.
Key Columns
| Column | Description |
|---|---|
| Payment Number | Unique payment identifier |
| Invoice Number | Invoice, SC, or Amazon internal reference |
| Description | Amazon's description (basis for Category Mapping) |
| Net Amount Paid | Final impact of the payment event |
| Type (Mapped Category) | INVOICE, CHARGEBACK, RETURN, PROVISION, etc. |
| Pattern | Keyword rule used to classify the row |
| Present in Invoicing | Whether this line is linked to an invoice in the Invoicing tab |
Remittance feeds all other Vendor modules: Invoicing (shortage/correction detection), Payment Cycle (SC/SCR events), and Recap Costi Extra (monthly category totals).
CHAPTER 9.9Return Remittance Payment Cycle
A dedicated version of the Payment Cycle, pre-filtered exclusively for VRET (Vendor Return) lines. It shows which VRET invoices were generated, how they were paid, and in which payment cycle they were settled.
Clicking the expand arrow on each row opens a detail panel with: Invoice Number, Total Invoice Amount, Total Amount Paid, and a full payment breakdown with dates and net paid amounts.
CHAPTER 9.10Return SummaryVENDOR
Return Summary aggregates returns on the Vendor channel, giving the volume and value of returned goods behind the return remittance figures.
CHAPTER 9.11Payment Recap
The Payment Recap shows a summary of every Amazon Vendor payment — total amount paid, payment date, currency, and type (EFT). Each row represents one Amazon payment number.
To understand what makes up a payment total, copy the Payment Number and search for it in Remittance Listing to see the full invoice-level breakdown.
CHAPTER 9.12Disputes & Disputed PO
Disputes
The Disputes module tracks all Amazon Vendor disputes (Vendor Returns, Shortage Claims, Invoice disputes). Each row shows Dispute ID, Type, Status (Open/Closed), Total Dispute Amount, and Approved Amount.
Approved Amount = Total → fully won · Approved Amount = 0 → fully rejected · Status = Closed, Approved < Total → closed but not fully reimbursed
Disputed PO
Links disputes to their associated Purchase Orders, creating a complete chain: PO → Invoice → Dispute → Outcome. Shows which PO lines are referenced, how much was disputed, and how much was approved.
CHAPTER 9.13Disputed POVENDOR
Disputed PO narrows the dispute process to the purchase-order line level: which products within a PO are contested, in what quantity and value.
Amazon resolves shortage claims per line, so a dispute is only actionable when it is expressed at this granularity.
CHAPTER 9.14Chargeback Dashboard
Provides a complete visual overview of all chargeback-related financial activity from Amazon Vendor Central.
KPI Strip
| KPI | Meaning |
|---|---|
| Dispute Approved | Amounts won back from Amazon |
| Dispute Denied | Amounts lost after dispute |
| Charged | Amounts Amazon charged directly |
| Notification Only | Amazon notifications — no financial impact |
| Dispute in Review | Amounts under review |
| Pending Invoice | Chargebacks appearing on a future invoice |
Common Issue Types
ASN Accuracy, PO On-Time Accuracy, Carton Information Compliance, Carton Content Accuracy, Labeling Accuracy, Packaging Accuracy, Delivery Appointment Issues
Total Calculation Rule
Total = Charged + Dispute Denied + Dispute in Review. Notification-only statuses are excluded from the Total — they have no financial impact.
CHAPTER 9.15Chargeback Detail ViewsVENDOR
Beyond the chargeback dashboard, four views break the same chargeback data down for investigation and for building a claim.
| View | Purpose |
|---|---|
| Chargeback | The full list of chargebacks applied by Amazon |
| Recap Tabellare | Tabular recap, aggregating chargebacks for reporting |
| Ordini | Chargebacks attributed to orders, also viewable grouped by problem type |
| Asin | Chargebacks attributed to ASINs, also viewable grouped by problem type |
The problem-type groupings matter: a chargeback category that repeats across many orders usually indicates a systematic process issue that can be challenged as a whole, rather than case by case.
CHAPTER 9.16COOP Module
The COOP module centralizes all Cooperative Marketing data from Amazon Vendor Central, enhancing it with VAT logic, agreement classification (ORDINARY vs DEAL), and full audit capabilities.
COOP Navigation Path
Vendor → Reports → COOP → Dashboard / Invoices / Agreement / Agreement PO / Remittance
COOP Workflow (Step by Step)
Import COOP Excel from Amazon Vendor Central (Payments → CoOp → Deductions) into COOP → Invoices via the Actions button.
Click Perform Calculation (yellow button) to trigger the calculation engine — this populates the Dashboard, Agreement, and Agreement PO views.
For each invoice, go to Amazon Vendor Central, search by Invoice ID, and download the backup Excel report.
Return to COOP → Invoices and click Upload on the invoice row to attach the backup report. This enables the Agreement PO breakdown.
Verify cash deduction in COOP → Remittance — confirm the Debit Note was actually deducted from an Amazon payment.
COOP Invoice Key Columns
| Column | Description |
|---|---|
| Invoice ID | IDs starting 5800 = Debit Notes (no VAT); 222/203 = Fiscal Invoices (VAT included) |
| VAT Included | Auto-detected based on invoice numbering |
| Agreement ID | Primary key linking invoice → agreement → PO → Dashboard |
| Funding Type Category | ORDINARY (recurring) or DEAL (one-off promotional) |
| Net Original Balance | Net value after VAT separation |
| Child Report Uploaded | Yes/No — backup report attached for audit |
Without completing the COOP Invoices page correctly (COOP Excel import + backup report uploads + Perform Calculation), the Dashboard, Agreement Listing, and Agreement PO views will be empty or incorrect.
CHAPTER 9.17COOP ViewsVENDOR
The COOP module is organised into six views covering the agreement lifecycle.
| View | Purpose |
|---|---|
| Dashboard | Overall COOP position across agreements |
| Invoices | COOP activities and the invoices raised against them |
| Agreement | The agreements themselves and their terms |
| Agreement PO | Agreements linked to purchase orders |
| Remittance | COOP remittance and settlement |
| Agreement Month Stats | Monthly statistics per agreement |
COOP submissions are sent from Send Document.
CHAPTER 9.18Account SummaryVENDOR
Account Summary rolls the vendor financial picture up to account level, in two complementary views.
| View | Shows |
|---|---|
| Invoice | Invoiced and paid position per account |
| Chargeback | Aggregate chargeback exposure per account |
This is the reporting layer for the vendor business: the level at which performance is discussed with Amazon and internally.
CHAPTER 9.19Vendor Orders (Purchase Orders)Vendor
Displays all Amazon Vendor purchase orders. Access via Vendor → Orders → Purchase Orders.
PO Table Columns
Purchase order number, state, date, state change date, type, vendor code, fulfillment center, delivery window start/end, ordered/accepted/rejected/received quantities, net cost amount, ordered/accepted revenue.
PO Synchronization
Purchase orders sync automatically every day. Click SYNCHRONIZE for a manual refresh. First load retrieves 6 months of PO history.
Available Exports
- Export All (Excel / CSV)
- Export To Ship (Excel / CSV) – Internal operational export
CHAPTER 9.20PO ManagerVENDOR
PO Manager is the operational workspace for purchase orders — the place where a PO is confirmed, prepared and dispatched, as opposed to the PO List which simply shows them.
Review the purchase order and confirm the quantities you can supply.
Prepare the shipment against the confirmed lines.
Create the courier shipment and dispatch, with the shipment recorded against the PO.
Confirmed quantities that are not delivered become shortage claims and chargebacks later. It is cheaper to confirm accurately than to dispute afterwards.
CHAPTER 9.21PO Invoice, History & JSON ViewerVENDOR
Three supporting views around purchase-order invoicing.
| View | Purpose |
|---|---|
| PO Invoice | Invoice status per purchase order — invoiced, pending, or problematic |
| PO Invoice Accounts | The same invoice-status performance aggregated by account |
| PO History | The historical record of purchase orders |
| JSON Viewer | The raw purchase-order payload as received from Amazon |
The JSON Viewer is a diagnostic tool. When a PO displays unexpectedly, it shows exactly what Amazon sent, which distinguishes a data problem from a display problem.
CHAPTER 9.22Send Document & Submit COOPVENDOR
Send Document is the outbound channel to Amazon: the module used to submit documents, including COOP submissions, from within the platform.
Submit COOP is the dedicated flow for COOP agreement submissions, working alongside the COOP module.
Documents sent from here go to Amazon. Confirm the content and the target account before submitting — a submission cannot be recalled from the platform.
CHAPTER 9.23Buy Box – VendorVendor
Monitors Buy Box ownership at ASIN level for Vendor accounts. Data is refreshed daily (~24-hour intervals).
Vendor Buy Box Logic: If Amazon is the Buy Box winner → Buy Box is considered WON.
Key Metrics
| Metric | Description |
|---|---|
| BuyBoxWinner % | % of time Amazon held the Buy Box in the selected window |
| BB / Cost Diff | Buy Box Price ÷ Product Cost (margin pressure indicator) |
| BB / Gross Diff | Buy Box Price ÷ Gross Price (competitive aggressiveness) |
| 30d Acc Turnover | Accepted sell-in turnover last 30 days |
CHAPTER 9.24Listing IssuesVENDOR
The vendor view of listing issues: products that are blocked, suppressed or otherwise unable to sell on Vendor Central.
The mechanics mirror the seller equivalent described in Listing Issues, applied to the vendor catalog. Any product listed here is generating no revenue while the issue persists, which makes it the highest-value list to clear.
CHAPTER 9.25Pricing Analytics – VendorVendor
Provides a line-by-line cost and pricing breakdown. Key calculated columns:
- Dimensional Weight = (Longest × Median × Shortest Side) ÷ 5000 kg
- Net Cost Amount = (Product Cost + Chargeback + Fee BS + Shipping + Logistic Prep) × (1 + COOP Markup)
- Net Selling Price = Net Cost Amount + Amazon Markup
- Gross Selling Price = Net Selling Price × VAT
- Amazon Margin % = Amazon Margin ÷ Net Selling Price
CHAPTER 9.26Vendor Inventory – ForecastingVendor
Provides a monthly inventory coverage and reorder validation view. BetterShop calculates total shipped units, available inventory, open PO units, and customer returns to derive a 1-Month Stock Target Coverage.
Color Code
- 🟧 Orange – Units leaving the warehouse (monthly shipped)
- ⬜ Grey – Stock on hand
- 🟩 Green – Incoming units (open POs, customer returns)
- 🟨 Yellow – Calculated aggregates (Net Consumption, Stock Target)
Although labeled "Forecast Inventory", this module currently provides average reorder logic and monthly stock coverage control. True predictive forecasting is still under development.
CHAPTER 9.27Forecast VendorVENDOR
Forecast Vendor projects expected demand on the Vendor channel, complementing the replenishment view: replenishment addresses what to send now, the forecast addresses what will be needed.
The numbers here are retrieved from Amazon's own demand forecast per ASIN. BetterShop stores and presents them — it does not model demand itself. When a figure looks wrong, it is Amazon's view of your product that is wrong, and the lever is the commercial conversation, not a setting in this page.
Mean, P70, P80, P90
Every ASIN and period carries four figures. They are not alternative estimates of the same thing — they are the same distribution read at different confidence levels:
| Figure | What it means |
|---|---|
| Mean | The expected value. Actual demand lands above it about as often as below it |
| P70 | Demand is expected to fall at or below this quantity in roughly 70% of outcomes |
| P80 | The same at 80% — a larger number, covering more of the upside |
| P90 | The same at 90%. The most cautious figure, and the largest |
Planning to the mean means being short roughly half the time. Planning to P90 means holding stock that is usually not needed. The percentile you choose is a stock-out versus overstock decision, not a forecasting one.
Choosing the Model in Replenishment
The choice is not confined to this page. Replenishment takes a forecast model — MEAN, P70, P80 or P90 — and the selected one becomes the demand input to its suggestions, aggregated per product and month. Switching the model changes the replenishment figures across the board, which is why two people comparing numbers should confirm they are on the same model before assuming a discrepancy.
Generation Date vs Period
Each row records both the period it covers (start and end date) and the date Amazon generated it. These are independent: the same future week can be forecast repeatedly as it approaches, and the estimate typically moves. A record is keyed on account, marketplace, ASIN and period — so a fresh retrieval for a period already held replaces it rather than accumulating alongside it, and the page always reflects Amazon's latest view.
Read with Sell In — forecast accuracy is judged against the purchase orders Amazon actually raises. A forecast that consistently runs above real purchase orders inflates any replenishment built on it.
CHAPTER 9.28Vendor Analytics – Performance ViewVendor
The main Vendor dashboard providing a Year-over-Year comparison of all key Vendor metrics: sell-in, sell-out, traffic, inventory, advertising, and profitability.
Always select a complete full year for accurate YoY comparison. Partial periods produce misleading deltas. The system automatically compares the selected year vs the same period of the previous year.
KPI Groups
| Group | KPIs |
|---|---|
| Retail (Sell-Out) | Shipped Revenue, Shipped Units, Average Selling Price (ASP) |
| Sell-In (to Amazon) | Total Sell-In Value, Sell-In Volume |
| Shipped COGS | Shipped COGS, ASP Shipped COGS (margin pressure) |
| Traffic & Conversion | Glance Views, Conversion Rate = Shipped Units / Glance Views |
| Inventory & POs | Inventory Available, Open Purchase Orders |
| Advertising | Ad Spend, Ad Sales |
| Profitability | PPM, Net PPM = Revenue – Shipped COGS |
CHAPTER 9.29Sell In (Order Analytics)VENDOR
Sell In is what Amazon buys from you — purchase order demand. It is the vendor equivalent of your own sales, and the basis of vendor revenue.
| View | Purpose |
|---|---|
| Dashboard | Headline sell-in position and trend |
| Products | Order analytics at product level |
| Accounts | Sell-in by account |
| Brands | Sell-in by brand |
| Sub Categories | Sell-in by category |
Sell In is what Amazon orders from you; Sell Out is what Amazon sells to consumers. When sell-in runs ahead of sell-out, stock is accumulating at Amazon and future orders will fall.
CHAPTER 9.30Sell Out (Retail Analytics)VENDOR
Sell Out is what Amazon sells to end customers — consumer demand for your products. It is the leading indicator for future sell-in.
| View | Purpose |
|---|---|
| Dashboard | Headline sell-out position |
| Products | Consumer sales by product |
| Accounts | Sell-out by account |
| Brands | Sell-out by brand |
| Sub Categories | Sell-out by category |
Retail Analytics Distribution View
A complementary set of views — Products, Accounts and Brands — presenting the same retail data from a distribution perspective, used to check how sales spread across the network rather than their total.
CHAPTER 9.31Net PPMVENDOR
Net PPM (Pure Product Margin) is Amazon's measure of the profitability of your products to Amazon itself. It drives how Amazon treats your range: products with weak Net PPM attract pressure on price, reduced ordering, or delisting.
Views
| View | Purpose |
|---|---|
| Account View | Net PPM aggregated per account |
| Brand View | Net PPM by brand |
| Products | Net PPM at ASIN level — where action is taken |
| Sub Category View | Net PPM by category |
Net PPM Distribution View
A parallel set of Account, Brand and Product views presenting Net PPM from a distribution perspective.
Net PPM is the metric Amazon uses in vendor negotiations. Knowing which of your ASINs are dilutive before the conversation starts is what allows you to propose a remedy rather than accept a demand.
CHAPTER 9.32Vendor Order Analytics
Analyzes sell-in data (brand → Amazon), not final customer sales. Access via Vendor → Analytics.
Dashboard Charts
- Ordered Quantity & Turnover – Volume and revenue trend
- Accepted Quantity & Turnover – What was actually accepted
- Ordered vs Accepted Comparison – Gap identification with acceptance rate %
Products Table – Orders vs Turnover Toggle
The toggle switches between Quantities (Orders view: Ordered Qty, Accepted Qty, Net Cost) and Monetary Values (Turnover view: Ordered €, Accepted €, Net Cost). The table structure stays the same — only the meaning of the values changes.
CHAPTER 10.1TikTok Shop OverviewTIKTOK
TikTok Shop is the third workspace in BetterShop. Selecting it in the app switcher replaces the Amazon-specific menus with TikTok's own orders, finance and analytics modules.
What Is Different
TikTok Shop is a content-driven marketplace: sales originate from videos and live streams rather than from search. The analytics reflect that — alongside the usual commercial metrics you will find engagement, viewership and creator performance, because on TikTok they are the demand drivers.
| Area | Modules |
|---|---|
| Orders | TikTok order listing |
| Reports | Statements, Settlement Reports, Profit & Loss, Finance History |
| Analytics | Shop Performance, Content Analytics, Inventory & Sales, Audience |
Amazon-only areas are hidden in this workspace: Amazon Ads, Market Analysis, Keywords Analysis, Inbound Plans and Category Mappings.
CHAPTER 10.2TikTok OrdersTIKTOK
The order listing for TikTok Shop: orders received, their status and their value. It is the operational counterpart to the settlement reports, which describe what was actually paid out.
CHAPTER 10.3Settlement & StatementsTIKTOK
Three views cover the money side of TikTok Shop, from raw statement to derived profitability.
Statements
The statements TikTok issues — the source record of amounts due and paid.
Settlement Reports
The processed settlement view: what was settled for a period, and the deductions applied to reach the net figure.
Profit & Loss
The profitability result for the TikTok channel, taking settled revenue against product and channel costs.
Statements are the source, Settlement Reports the reconciliation, Profit & Loss the outcome. When a P&L figure looks wrong, work backwards through that chain.
CHAPTER 10.4Finance HistoryTIKTOK
Finance History is the archive of TikTok financial events over time — the record behind the settlement views, used to trace a figure to its origin or investigate a period-to-period discrepancy.
CHAPTER 10.5Shop PerformanceTIKTOK
The Shop Performance overview is the headline view of the TikTok channel, presented as KPI cards with a GMV breakdown and trend charts.
KPI Cards
| KPI | Meaning |
|---|---|
| Sales GMV | Gross merchandise value of sales |
| Gross Revenue | Revenue before deductions |
| Items Sold | Units sold |
| SKU Orders / Orders | Orders at SKU level and in total |
| Avg Customers | Average customers over the period |
| Refunds / Refund Rate | Refunded value and its share of sales |
| Avg Order Value | Average value per order |
| Page Views / Avg Visitors | Traffic reaching the shop |
| Avg Conversion Rate | Share of visitors who purchase |
GMV Breakdown
A breakdown of where GMV originates, which on TikTok is the key structural question: how much of the channel is carried by video, by live, and by the product pages themselves.
CHAPTER 10.6Content AnalyticsTIKTOK
Content Analytics measures the content that generates sales, in two views.
Video Performance
Performance of individual videos, combining commercial and engagement metrics: Sales, Orders, Items Sold, Customers, Views, Likes, Comments, Shares, New Followers, Product Impressions, Product Clicks, Engagement, CTR and CVR. Videos are listed with their creator, hashtags, post time and duration.
LIVE Performance
Performance of live streams, with metrics specific to live selling: Sales GMV, Live 24h GMV, Avg Price, Click To Order Rate, Products Added, Different Products Sold, Created SKU Orders, SKU Orders, Items Sold, Customers, Views, ACU and PCU (average and peak concurrent users), Viewers and Avg Viewing Duration.
Engagement without CTR means content that entertains but does not sell. High CTR with low CVR points at the product page rather than the content. ACU and PCU show whether a stream held its audience or lost it.
CHAPTER 10.7Inventory & SalesTIKTOK
Two views connect demand to available stock.
Product Detail
| Column | Meaning |
|---|---|
| Product | The product |
| Traffic Views / CVR | Traffic reaching the product and its conversion rate |
| Sales / Orders / Items Sold | Commercial result |
| Canceled / Returned / Refunded / Replacements | Order outcomes after sale |
| Available Stock / Committed | Stock free to sell and stock already allocated |
| Status | Listing state |
SKU Performance
The same picture at SKU level — Product, GMV, Orders, Units Sold, Available Stock and Committed — which is the level at which stock decisions are actually made.
On TikTok a product can sell out within a single live stream. Available Stock read next to recent velocity is the practical early warning.
CHAPTER 10.8Customer InsightsTIKTOK
Customer Insights describes who is buying: age demographics, gender distribution and geographic distribution, presented as donut charts and a map.
On a content-driven channel this closes the loop — it shows whether the audience your content attracts is the audience that actually converts, and where to concentrate creator and campaign effort.
