Ascent Guide

The Ascent dashboard lives at www.ascentrepricer.com/dashboard/. Use this dashboard for account setup, billing, marketplace settings, listings, orders, history, workflows, and repricing controls.

After signup, Ascent sends a welcome email with a secure link to create your password. Once your password is set, sign in to the dashboard with the same email you used at checkout.

The first-time setup panel shows the checks that matter before automation is trustworthy: Amazon connection, listings, COG coverage, repricing status, workflow preview, and subscription access.

New users should use the welcome email to create a password. Existing users can use Forgot password on the dashboard login page if their old app password does not work.

The reset link is sent to the billing email on your Ascent account. If you do not see it, check spam first, then contact support.

If Ascent does not yet have your Amazon refresh token, the dashboard will ask you to choose your main marketplace and authorise Ascent in Seller Central.

After Amazon redirects you back to the dashboard, Ascent creates your user folder, saves the refresh token, and starts using that account data for the dashboard.

Home is the first page you see after login. It gives you the high-level health of the account without making you dig through every listing.

Use the time period controls to switch between short-term movement and longer-term trends. The goal is to spot whether Ascent is winning Buy Box, protecting margin, and moving stock as expected.

If Buy Box wins are low, inspect the Listings page and History page before changing rules. The issue may be price, stock, marketplace coverage, or missing COG data.

If many listings are at minimum, your rule criteria may be too strict, your COGs may be wrong, or the market may simply be too competitive for those SKUs.

Home shows a short preview of recent pricing actions. Use it for a quick scan, then open History when you need the full audit trail.

A price increase that later comes back down is not automatically a problem. Ascent tests the market, then adjusts when the Buy Box or competition changes.

Listings is where you manage the actual SKUs Ascent is repricing. It is designed for fast filtering, targeted edits, and exception handling.

You can search by SKU, ASIN, title, or rule, then narrow the view using status filters such as Missing COGs, Winning Buy Box, At Minimum, Suppressed Buy Box, Repricing, Not Repricing, and FBM.

You do not need to add a currency symbol when entering cost or price values.

Use Missing COGs first during setup. Ascent needs reliable COG data to calculate profit and ROI correctly.

Use At Minimum to find listings where your guardrails are stopping further price drops. Use FBM when you want to review merchant-fulfilled listings separately from FBA listings.

Click the edit control on a listing to open the edit popup. Save changes before closing the popup; unsaved edits are not applied.

If you manually change the rule on a SKU, it becomes a manual override. The selector only offers rules that exist in the active workflow, and the override uses the matching workflow criteria rather than the old default rule criteria.

Use Reset to age automation when you want that SKU to stop using its manual rule and follow the workflow age ranges again.

The CSV setup import can update guardrails in bulk. Ascent previews matched, unmatched, and invalid rows before applying changes, so check the preview carefully before confirming.

Imported rule values must be valid for the active workflow. Rows using a rule that is not currently active are rejected instead of silently creating a bad override.

Your listing minimum price is not the only safety net. Ascent also respects the minimum profit and ROI criteria set in Settings.

For example, if a listing has a GBP 0 minimum price but your Settings criteria require GBP 3 profit, Ascent will still avoid prices that fail the GBP 3 profit rule.

Orders shows recent Amazon order activity alongside profitability context. It helps you understand what sold, whether the sale was healthy, and which SKUs deserve attention.

Use Orders after checking Home when you want to connect dashboard metrics to actual sales.

If a SKU is selling but profit is weaker than expected, open Listings and review its COG, minimum price, maximum price, VAT setting, and rule.

If a SKU is not selling, compare Orders with History. The listing may need a more aggressive rule, a lower minimum, or simply more time in the market.

Use Export CSV when you want to review order data outside Ascent or share it with a spreadsheet workflow.

History is the full audit trail for Ascent repricing actions. Use it when you want to know what changed, when it changed, and why.

This is the best page for troubleshooting unusual movement on a SKU because it shows the reason attached to each action.

Search by title, ASIN, SKU, or reason to isolate one listing or one type of repricing behaviour.

Use Export CSV if you want to inspect the audit trail in a spreadsheet or keep a local record.

If a listing looks too low, search the SKU in History and read the latest reason. Then check Listings for COG, VAT, min price, max price, workflow rule, and whether the SKU has a manual override.

If a listing keeps hitting minimum, inspect whether the criteria are too strict or whether the market has moved below your profitable floor.

When a SKU has a manual rule override, History shows the rule used for the action. Use that rule together with the active workflow to understand which profit and ROI criteria were applied.

After changing workflow rows or resetting a manual override back to age automation, check History on the next repricing cycle to confirm the SKU is following the expected criteria.

Settings is where you define account-level behaviour. This page controls billing access, marketplace coverage, VAT, Auto COG, repricing automation, workflow templates, custom workflow rows, and API keys.

Getting Settings right matters because these values become the safety rails for every listing unless you create a listing-level manual override.

The setup panel at the top of the dashboard summarises account readiness. It checks Amazon connection, listings, COG coverage, repricing status, workflow preview, and subscription access.

Use Review automation to inspect the account-level repricing switch. Use Review workflow to jump directly to the workflow editor rows.

The top of Settings shows the signed-in account, email, primary marketplace, enabled marketplace count, plan, and billing status.

Use Manage Stripe billing or Manage Whop billing to open the correct billing portal for your account. If billing management is unavailable, contact support from the dashboard.

Enter your VAT rate as a percentage, then click Save fees. If you are not VAT registered, use 0. If you are VAT registered, use your actual rate, such as 20 for UK standard VAT. This changes profit calculations, so do not guess.

Auto COG is controlled from Settings, in the Automation panel. Turn Auto COG on, click Save automation, then let Ascent pick it up on the next inventory refresh. It fills the COG field for new listings when the cost is already built into the SKU.

Ascent reads the second part of the SKU as the cost. The SKU must use one separator style consistently: dashes only or underscores only. Do not mix dashes and underscores in the same SKU for Auto COG, because mixed SKUs are skipped to avoid pulling the wrong number.

After enabling Auto COG, open Listings and use the Missing COGs filter. Supported new SKUs should have their cost filled automatically; anything still shown there needs a manual COG or a cleaner SKU format.

If a SKU uses a supplier format, marketplace prefix, bundle code, or mixed separators, do not assume Auto COG has understood it. Check the COG before letting repricing depend on it.

Choose a workflow template when you want a sensible starting point for age-based repricing. Templates map stock age ranges to rules, profit floors, and ROI floors.

The workflow preview uses listing age data to show how the template will affect the account. Review the projected impact before saving, especially on accounts with ageing stock or many manual overrides.

Custom workflow rows let you edit the rule order, age windows, minimum profit, and minimum ROI before saving the strategy. This is now the main place to configure account-level repricing behaviour.

Age automation uses these rows to decide which rule a listing should follow as stock gets older. Manual listing overrides still win until you reset that SKU back to age automation.

If a workflow contains the same rule more than once, manual listing overrides use the first matching row. That behaviour is intentional, so avoid duplicate rule names unless you are comfortable with the first row being the manual-override target.

Choose your primary marketplace and enable only the countries you actively sell in. Unavailable countries are hidden automatically.

For non-default marketplaces, set a fallback rule, minimum profit, and minimum ROI. Keep these minimums realistic, especially where returns, fees, or cross-border costs are higher.

The API access panel lets you create one customer API key for external tools, reporting, or AI agent workflows.

Copy the key when it is shown. For security, the full value is only displayed immediately after create or refresh. Refreshing or deleting a key will stop connected integrations that use the old key.

Ascent includes four repricing rules: Sicilian, Vienna, Gambit, and Marshall. Each rule has a different balance of profit protection and sales aggression.

Rules now live inside the active workflow. The workflow decides the age range, profit floor, and ROI floor for each rule row, and Listings uses that workflow when applying manual SKU overrides.

A workflow is an ordered set of rule rows. Each row contains a rule name, an age window, a minimum profit floor, and a minimum ROI floor.

When a SKU follows age automation, Ascent chooses the row that matches the SKU age. When a SKU has a manual rule override from Listings, Ascent matches that rule against the active workflow and uses the matching row criteria.

Sicilian is the least aggressive rule and is designed to protect margin. It is a sensible starting point for listings where profitability matters more than speed of sale.

Vienna is the balanced rule. Use it when you want steady Buy Box competition without pushing as hard as the more aggressive rules.

Gambit is aggressive and sales-focused. It competes harder for the Buy Box and is useful when you want stronger stock movement.

Marshall is the most aggressive rule. Use it for maximum sales pressure or ageing stock that needs to move, knowing that profitability may be lower.

A common approach is to start with Sicilian or Vienna, move to Gambit as stock ages, and reserve Marshall for stock that needs the strongest push.

Manual listing overrides should be used only for genuine SKU exceptions. The override still uses the active workflow criteria for that rule rather than separate legacy criteria.

If the same rule appears more than once in a custom workflow, a manual override uses the first matching row. This is explicit product behaviour, not a bug.