PROBINSIYANONG VA

Amazon Seller VA Training Curriculum

Complete Roadmap v2  ·  2026 Edition

From Zero to Process Owner

Amazon Seller Central Operations  |  Filipino Aspiring VAs

"From the province, for the province — and ready for the world."

Table of Contents

1. Program Vision        2

2. Who This Roadmap Is For        3

What Role This Roadmap Prepares Them For        3

3. Training Philosophy        3

4. Capability Levels        5

5. Roadmap Overview        6

6. The Full Curriculum (Detailed)        7

Phase 0 — Orientation & Amazon VA Role Awareness        7

Module 0.1 — What an Amazon Seller VA Actually Does        7

Module 0.2 — Work Ethics, Client Trust & Keeping the Job        8

Phase 1 — Seller Central Foundation & Daily Operating Rhythm        11

Module 1.1 — How Amazon Seller Central Works as a Business System        11

Module 1.2 — Seller Central Navigation & Page Familiarity        12

Module 1.3 — Daily Account Check Routine        14

Module 1.4 — Issue Classification: What Kind of Problem Is This?        15

Phase 2 — Catalog, Listing & Offer Operations        18

Module 2.1 — ASIN, SKU, FNSKU, UPC & Variation Fundamentals        18

Module 2.2 — Product Detail Page Components & Listing Build Basics        19

Module 2.3 — Listing Status, Lifecycle & Suppressed Listings        21

Module 2.4 — Listing Edits, Flat File Awareness & Contribution Conflicts        22

Module 2.5 — Offer Health Basics: Price, Buy Box & Sellability Checks        24

Phase 3 — Inventory & Fulfillment Operations        26

Module 3.1 — FBA vs FBM Operations & Inventory Status        26

Module 3.2 — Inventory Health, Low-Stock Monitoring & Restock Awareness        27

Module 3.3 — Stranded Inventory, Inbound Shipment Monitoring & Receiving Discrepancies        28

Module 3.4 — Unfulfillable Inventory, Removal Orders & Inventory Cleanup Awareness        30

Phase 4 — Orders, Account Health & Post-Purchase Risk Monitoring        33

Module 4.1 — Order Issue Awareness, Returns & Refunds Basics        33

Module 4.2 — Voice of the Customer, Return Reasons & Product/Listing Quality Signals        34

Module 4.3 — Account Health, Policy Warnings & Compliance Risk Awareness        35

Phase 5 — Seller Support, Reimbursements & Issue Resolution Workflows        38

Module 5.1 — Seller Support Case Management        38

Module 5.2 — Evidence Gathering for Amazon Cases        39

Module 5.3 — FBA Reimbursements, Lost Inventory & Discrepancy Follow-Up        41

Module 5.4 — Case Follow-Up Discipline, Escalation Paths & Resolution Logging        42

Phase 6 — Reporting, Communication & Documentation        44

Module 6.1 — Reading Operational Reports & Dashboards        44

Module 6.2 — Daily Summaries, Weekly Reports & Client Updates        45

Module 6.3 — Issue Summaries, Escalation Notes & Professional Written Communication        47

Module 6.4 — Logs, Trackers & Documentation Discipline        48

Phase 7 — SOPs, Recurring Workflow Management & Process Ownership        50

Module 7.1 — SOP Writing for Amazon Seller VA Work        50

Module 7.2 — Recurring Workflow Management        51

Module 7.3 — Root-Cause Thinking & Process Improvement        52

Module 7.4 — Handoff Readiness & Process Owner Final Simulation        54

7. Recommended Training Deliverables Per Phase        56

8. Recommended Teaching Format for the Facebook Group        57

Per-Module Lesson Structure        57

Recommended Weekly Training Flow        57

9. What a Job-Ready Graduate of This Roadmap Should Be Able to Do        59

Seller Central Operations        59

Catalog & Listing Work        59

Inventory & Fulfillment Work        59

Order & Account Health Monitoring        59

Seller Support & Issue Resolution        59

Reporting & Communication        60

Process Ownership        60

1. Program Vision

This curriculum is designed for Filipino aspiring Amazon Seller VAs who want a clear, practical, job-oriented path into Amazon Seller Central Operations work.

This is NOT a course built around random Amazon terms.

This is a roadmap built around actual Seller Central work buckets.

The work buckets this roadmap covers:

• Checking listing health
• Monitoring inventory
• Spotting order and account health risks
• Handling Seller Support cases
• Documenting issues clearly
• Reporting clearly to clients
• Building SOPs and checklists
• Eventually owning a recurring workflow end-to-end

The goal is not just for the trainee to say: "Alam ko ang ASIN, SKU, at FBA."

The goal is for the trainee to become the kind of VA a client can trust to say: "Na-check ko na ang account. Eto ang issues. Eto ang evidence. Eto ang next step. Eto ang kailangan i-escalate." That is the standard this roadmap is aiming for.

2. Who This Roadmap Is For

• Beginners with zero Amazon Seller Central experience
• Aspiring Amazon VAs who want to work in Seller Central Operations
• Learners who want practical, real-task training instead of pure theory
• Probinsiyanong VA community members who want a structured path: Beginner → Task-based VA → Independent VA → Process Owner

What Role This Roadmap Prepares Them For

This roadmap prepares trainees for the Amazon Seller Central Operations VA role — also called:

• Amazon Seller VA
• Amazon Store Operations VA
• Seller Central VA
• Amazon Admin VA
• Amazon Operations Assistant

This roadmap is NOT primarily for:

• ✗  Amazon PPC Specialists
• ✗  Copywriters
• ✗  Amazon Graphic Designers
• ✗  Amazon DSP / External Traffic Specialists

Those are separate specialization tracks.

What This Roadmap Does NOT Cover Deeply

This roadmap is intentionally focused on Amazon Seller Central Operations VA work. It gives awareness where needed, but it does not aim to deeply train the following as primary specializations:

• Amazon PPC strategy and campaign management
• Listing copywriting, image design, or A+ content creation
• Advanced reimbursement auditing beyond standard operations support
• Brand Registry, legal / IP complaint management, and advanced compliance workflows
• Large-scale catalog management via complex flat files as a primary specialization
• Marketplace expansion / international compliance strategy

These may become separate future specialization tracks, but they are not the main scope of this roadmap.

3. Training Philosophy

The Probinsiyanong VA training program follows five non-negotiables:

1. Real work first, not jargon first

We don't learn Amazon terms just to memorize definitions. We learn them because they affect actual work.

2. Seller Central before fancy tools

The trainee must understand the business system and the workflows inside Seller Central first, before depending on outside tools.

3. Monitoring + judgment + communication

A good Amazon Seller VA is not just someone who can click buttons. They must know how to spot issues, classify urgency, gather evidence, document findings, update the client clearly, and know when to act vs. escalate.

4. Work ethic matters

This roadmap does not only teach how to get the job. It also teaches the habits needed to keep the job: consistency, documentation, follow-through, humility, escalation judgment, and respect for access and client trust.

5. Process ownership is the end goal

The ideal graduate is not just a task-doer. The ideal graduate can eventually own a recurring workflow end-to-end.

4. Capability Levels

The roadmap progresses through four capability levels:

5. Roadmap Overview

Eight phases, twenty-six modules — progressing from zero knowledge to process ownership.

6. The Full Curriculum (Detailed)

Phase 0 — Orientation & Amazon VA Role Awareness

Outcome: The trainee understands the role, the work environment, the expectations, and the difference between "learning Amazon" and "working responsibly inside a client account."

Module 0.1 — What an Amazon Seller VA Actually Does

Before touching Seller Central, the trainee needs a clear mental model of the role itself. If they misunderstand the role, everything else becomes confusing.

Learning Objectives

• Explain in plain language what an Amazon Seller VA does
• Distinguish a Seller Central Operations VA from a PPC Specialist, Copywriter, or Designer
• Identify the common work buckets of a Seller VA
• Describe what 'helping a seller run the account' means in practice
• Explain what 'process ownership' means at a VA level

Core Concepts

• Amazon Seller Central: The platform where Amazon sellers manage their store operations such as listings, inventory, orders, account health, support cases, and business reporting. Advertising tools exist within the Amazon ecosystem, but PPC is a separate specialization track and is outside the main scope of this roadmap.
• Seller VA vs PPC VA vs Copywriter: Different roles, different skills — the operations VA focuses on running the account, not writing content or managing ads
• Client / brand / agency / aggregator: The types of employers who hire Amazon VAs and what each relationship looks like
• Recurring tasks vs process ownership: Task-based means doing assigned tasks; process ownership means being responsible for a full recurring workflow
• Scope of work: VA responsibilities are defined clearly — knowing what is and is not your job is critical to safe, effective work
• Trust, access, and account responsibility: Access to a client's Seller Central account is a privilege. Handle it with care.

Practical Tasks

• ✓  Write a 5-sentence answer (in Filipino or English) to: 'Ano ang ginagawa ng Amazon Seller VA?'
• ✓  Given 15 sample tasks, classify which belong to: Seller VA / PPC VA / Copywriter / not the VA's responsibility
• ✓  Read a sample job post and identify: hard skills required, soft skills required, recurring responsibilities
• ✓  Write a short reflection: 'What kind of VA do I want to be in 6 months?'

Seller Central Pages, Reports & Tools to Know

• Amazon Seller Central homepage (overview only)
• Sample Amazon VA job postings on Upwork, OnlineJobs.ph, or LinkedIn
• Probinsiyanong VA community resource list

Common Beginner Mistakes

• ⚠  Thinking 'VA work = just clicking around in Seller Central' — it requires judgment, documentation, and communication
• ⚠  Confusing the Seller VA role with PPC or copywriting
• ⚠  Assuming all VA work is the same regardless of client size or business model

Suggested Mock Exercises / Training Activities

• Role Sorting Exercise: Given a list of 15 tasks, sort them into the correct VA role category
• VA Day-in-the-Life Mapping: Write out what you think a VA does in a client account on a Monday morning
• Facebook Group Discussion Post: 'What made you want to become an Amazon VA?' — respond to at least 2 classmates

Module 0.2 — Work Ethics, Client Trust & Keeping the Job

A beginner may get hired because of potential, but they keep the job because of reliability. This module sets the professional culture early — before any Seller Central training begins.

Learning Objectives

• Understand why documentation, consistency, and follow-through matter in real VA work
• Know the difference between 'marunong mag-click' and 'mapagkakatiwalaan sa trabaho'
• Understand escalation judgment and access responsibility
• Recognize common habits that cause VAs to lose client trust

Core Concepts

• Consistency over intensity: Showing up reliably every day is more valuable than doing a lot in one week and disappearing the next
• Documentation habit: If it's not written down, it didn't happen — this is the golden rule of VA work
• Asking before assuming: When unsure, ask. Acting on assumptions in a client's account can cause real damage
• Client confidentiality: Account access, business data, and client information are confidential — always
• 'Do not touch what you do not understand': This is a career-protecting principle for every new VA
• Update the client before the client asks: Proactive communication builds trust faster than any other habit

Practical Tasks

• ✓  Review 10 sample VA mistakes and write what should have been done instead
• ✓  Write a sample client update message after discovering a problem you cannot fix on your own
• ✓  Reflect and write: 'What 3 habits will make a client trust me more?'

Common Beginner Mistakes

• ⚠  Not sending an update unless the client asks first — even a simple: 'Naka-check na, walang issues ngayon' builds trust
• ⚠  Trying to hide or silently fix an error instead of disclosing it — clients value honesty more than perfection
• ⚠  Being available but not communicating clearly — being online is not the same as being reliable

Suggested Mock Exercises / Training Activities

• VA Habits Self-Assessment: Rate yourself on 10 professional habits and identify 2 to work on
• Mistake Analysis Exercise: Given 10 VA scenarios, identify the mistake and write the better response
• Accountability Pledge: Write your personal commitment to professionalism as a Probinsiyanong VA

Module 0.3 — Permissions, Access & Safe Practice Rules

Before a trainee works inside a real Seller Central account, they need to understand one non-negotiable truth: seeing where something is does not automatically mean you should touch it. This module sets the safety rules for working inside a client account responsibly.

Learning Objectives

Understand that different Seller Central users have different permission levels

Recognize that not all pages, reports, or actions are available to every VA

Know the difference between viewing, documenting, suggesting, and executing

Understand when a trainee should stop and ask before taking action

Learn safe practice rules for training environments versus live client accounts

Core Concepts

User permissions: What a VA can see or do in Seller Central depends on the access granted by the client or account admin

Access does not equal authority: Even if a button is visible, the VA should only use it if the workflow, SOP, or client instruction allows it

Live account risk: Testing changes inside a live account can affect listings, pricing, account health, or customer experience

Document first, ask second, act last: If the trainee is unsure whether an action is safe or authorized, they should document the issue first and ask for guidance before acting

Safe training environments: Mock accounts, screenshots, templates, exports, and simulated exercises are safer learning environments than live client accounts

Client trust: Responsible handling of access is part of professionalism, not just technical skill

Practical Tasks

✓  Review 10 example Seller Central actions and classify each as: safe to observe / safe to document / ask first / do not touch without approval

✓  Write a short response to the prompt: “What should I do if I see a problem in a client account but I’m not sure I’m authorized to fix it?”

✓  Review a mock account scenario and identify which actions require approval before execution

Seller Central Pages, Reports & Tools to Know

Seller Central user permissions / account access context (awareness level only)

Probinsiyanong VA Daily Check Template

Probinsiyanong VA Issue Escalation Template

Common Beginner Mistakes

⚠  Clicking through a live account “to see what happens”

⚠  Assuming that visible access means permission to act

⚠  Editing listings, prices, or cases without understanding the workflow or approval rules

⚠  Treating training simulations and live client work as if they carry the same level of risk

Readiness Milestone

The trainee can explain how permissions, authority, and safe practice differ — and can identify when to observe, document, ask, or act inside a client account.

Suggested Mock Exercises / Training Activities

Permission Judgment Drill: Given 15 actions, classify each as observe / document / ask first / do not touch

Safe Practice Reflection: Write a 5-sentence explanation of why “document first, ask second, act last” protects both the VA and the client

Client Account Scenario Review: Read a mock issue scenario and identify what should be escalated before any action is taken

Capability Target: Level 1 — Awareness

Phase 1 — Seller Central Foundation & Daily Operating Rhythm

Module 1.1 — How Amazon Seller Central Works as a Business System

Seller Central is not just a menu. It is an interconnected business system. A listing issue affects sales. Inventory issues affect listing performance. Account health issues affect the entire business. A VA who understands these connections makes better decisions.

Learning Objectives

• Describe the 5 main operational areas of Seller Central
• Explain how listings, inventory, orders, account health, and support cases connect to each other
• Identify which area is affected by a given business issue
• Explain FBA vs FBM at a high conceptual level

Core Concepts

• Catalog / Listings: Where product listings are created and managed — the storefront for each product
• Inventory: Where stock levels and fulfillment status are tracked
• Orders: Where customer purchase activity and fulfillment status are visible
• Account Health: Where Amazon tracks performance metrics, policy warnings, and compliance risk
• Seller Support / Case Log: Where the VA or seller communicates with Amazon to resolve issues
• Buy Box (awareness): The section of the product page where customers click 'Add to Cart' — critical for conversions. Teach this only at an awareness level so the trainee understands its operational impact; advanced pricing strategy, Buy Box optimization, and PPC-related decisions are outside the scope of this beginner operations track.
• FBA vs FBM: FBA: Amazon warehouses and ships; FBM: seller ships directly — each has different VA monitoring responsibilities
• ASIN / SKU (intro): Amazon's ID for a product (ASIN) vs the seller's internal product code (SKU)

Practical Tasks

• ✓  Draw a simple map of the 5 Seller Central areas and draw arrows showing how they connect
• ✓  Given 10 sample scenarios, identify which Seller Central area is affected
• ✓  Navigate to each core section and write a one-sentence description of what it is used for
• ✓  Compare FBA vs FBM in a simple table of differences

Seller Central Pages, Reports & Tools to Know

• Catalog > Manage Inventory
• Inventory > Manage FBA Inventory
• Orders > Manage Orders
• Performance > Account Health
• Help > Case Log

Common Beginner Mistakes

• ⚠  Thinking each Seller Central section is independent — they affect each other significantly
• ⚠  Confusing SKU and ASIN from the start — establish this clearly
• ⚠  Not understanding that an inactive listing means zero sales for that product

Suggested Mock Exercises / Training Activities

• Seller Central Map Exercise: Draw a flowchart connecting the 5 main areas — note what happens in each when an order is placed
• Terminology Quiz: Match 15 Amazon terms to their correct definitions
• Navigation Practice: Navigate to 8 specific pages in under 10 minutes

Module 1.2 — Seller Central Navigation & Page Familiarity

A VA cannot monitor or troubleshoot what they cannot find. Seller Central has many pages and menus — knowing where to go for each type of check is a fundamental operational skill.

Learning Objectives

• Navigate core Seller Central menus without getting lost
• Locate the pages most commonly used by a Seller VA
• Understand which pages are checked daily vs weekly vs only when needed

Core Concepts

• Home Dashboard: Daily snapshot of sales, alerts, and account notifications
• Manage Inventory: Listing status, listing health, suppressed listings filter
• Manage FBA Inventory: FBA-specific inventory status, stranded, unfulfillable
• Manage Orders: Order status, pending, unshipped, late orders
• Account Health: All performance metrics and policy warnings in one place
• Voice of the Customer: Buyer feedback signals and return reasons by ASIN
• Case Log / Get Support: View and manage all Seller Support cases
• Inventory Planning / Restock: Restock recommendations based on sales velocity
• Fulfillment Reports: Inventory health, reconciliation, stranded inventory reports
• Business Reports: Sessions, units ordered, unit session percentage per ASIN

Practical Tasks

• ✓  Navigation Drill: Locate 10 specific pages in under 10 minutes
• ✓  Page Mapping Worksheet: For each page, answer — 'What is this page for? What issue would send me here?'
• ✓  Daily vs Weekly vs As-Needed: Classify the 10 pages above by check frequency

Seller Central Pages, Reports & Tools to Know

• All pages listed in Core Concepts above

Common Beginner Mistakes

• ⚠  Spending too long exploring menus without a clear purpose — always have a reason before clicking
• ⚠  Not bookmarking frequently used pages — navigation speed improves with practice and bookmarks
• ⚠  Confusing Manage Inventory with Manage FBA Inventory — they show different data

Suggested Mock Exercises / Training Activities

• Speed Navigation Drill: Timed exercise — reach 10 pages in the correct order as fast as possible
• Page Purpose Quiz: Given 10 screenshots, name the Seller Central page and describe one use case for it

Module 1.3 — Daily Account Check Routine

A consistent daily account check is the heartbeat of the Amazon operations VA role. This is the single habit that builds the most client trust, fastest. A reliable daily check means the client does not have to worry about missed alerts, suppressed listings, or account health drops going unnoticed.

Learning Objectives

• Know the key areas to check every day in a Seller Central account
• Explain why each check matters for account health and sales performance
• Complete a guided daily account check using a checklist
• Document check results in a log
• Know when to act, monitor, or escalate

Core Concepts

• Daily check areas: Listing status, inventory levels, inbound shipments, account health alerts, open support cases, order/late shipment risk (FBM), VoC signals (if relevant)
• Alert vs Warning: Some alerts are informational; others require immediate action — knowing the difference is critical
• Act vs Escalate vs Monitor: A VA should know which issues they can resolve directly vs. which need client or manager approval
• Documentation habit: Every daily check should produce a brief written record — not just a mental note

Recommended Daily Check Sequence

1. Account Health — check for warnings, policy issues, performance alerts, and urgent account risks

2. Manage Inventory / listing status — review inactive, suppressed, stranded clues, and listing health issues

3. Manage FBA Inventory / stock health — review available, reserved, inbound, unfulfillable, and stock-risk indicators

4. Inbound shipments / receiving issues — if the account uses FBA and has active inbound shipments

5. Case Log — check open cases, stalled cases, and new responses that need follow-up

6. Manage Orders / late shipment risk — especially for FBM accounts or accounts with current order issues

7. Voice of the Customer — if relevant to the account’s volume and current product quality / return trends

8. Write Daily Summary + update trackers — log findings, actions taken, and items requiring follow-up or escalation

Practical Tasks

• ✓  Complete a daily account check using the Probinsiyanong VA Daily Check Template
• ✓  Identify at least 2 items in a mock account that require action
• ✓  Fill out a Daily Check Log with findings
• ✓  Write a 3-sentence end-of-day summary to a client

Seller Central Pages, Reports & Tools to Know

• Performance > Account Health
• Catalog > Manage Inventory (filter by status)
• Inventory > Manage FBA Inventory
• Help > Case Log
• Orders > Manage Orders (pending, late)
• Performance > Voice of the Customer

Common Beginner Mistakes

• ⚠  Skipping the daily check when there is 'nothing urgent' — issues often appear quietly
• ⚠  Checking but not documenting — findings not written down are easily forgotten
• ⚠  Acting on every alert without checking if client approval is needed first

Suggested Mock Exercises / Training Activities

• Timed Daily Check Simulation: Given a mock account dashboard with planted issues, complete the full check in 20 minutes and submit a written summary
• Issue Classification Exercise: Given 10 Seller Central alerts, classify each as: (a) act directly, (b) monitor, (c) escalate
• 5-Day Documentation Challenge: Perform a simulated daily check for 5 consecutive days and maintain a log

Module 1.4 — Issue Classification: What Kind of Problem Is This?

Beginners often see 'something is wrong' but don't know what type of problem it is. Issue classification is diagnostic thinking — it is the mental skill that determines where to look first, what evidence to gather, and how urgent a response is needed. Training this early prevents wasted time and incorrect responses later.

Learning Objectives

• Distinguish between: listing problem, inventory problem, order problem, account health problem, offer/pricing/Buy Box problem, and support case / Amazon-side issue
• Identify the first page or report to check for each issue type
• Decide whether the VA can act, monitor, or must escalate for each issue type

Core Concepts

• Listing problem: Issue is with the product's catalog data — title, images, attributes, suppression status
• Inventory problem: Issue is with stock levels, stranded status, inbound shipments, or unfulfillable units
• Order problem: Issue is with order fulfillment, late shipments, returns, A-to-Z claims, or buyer disputes
• Account health problem: Issue is with performance metrics, policy compliance, or violation warnings
• Offer / pricing / Buy Box problem: The listing is live but the offer is not winning the Buy Box or the price is causing issues
• Amazon-side issue: Something Amazon must fix — a catalog error, receiving discrepancy, or technical glitch

Act / Escalate / Do Not Touch Guide

A. Usually safe to act on (if trained, authorized, and following the approved workflow)

Exporting reports and gathering evidence

Updating logs, trackers, and daily summaries

Identifying suppressed listings and documenting the exact reason

Monitoring inventory, inbound shipment status, stranded inventory, and open case status

Following up on existing Seller Support cases using an approved template

Drafting issue summaries and escalation notes for the client

B. Escalate before acting

Listing edits that change important product attributes, product claims, or compliance-sensitive fields

Pricing changes that could affect margin, Buy Box status, or customer experience

Parent-child variation changes

Reimbursement cases where evidence is incomplete or the discrepancy is unclear

Account Health warnings that may require a client decision or formal response

Any action that could significantly affect sales, compliance, customer experience, or brand reputation

C. Do not touch unless directly instructed, trained, or explicitly authorized

Policy appeals or Plan of Action submissions

Compliance responses involving authenticity, restricted products, or legal / policy risk

Brand Registry, IP complaints, or legal / rights-owner matters

Dangerous goods / hazmat / product compliance workflows

Large-scale flat file uploads into a live account without approval and review

Any action the VA cannot clearly explain before doing it

Practical Tasks

• ✓  Given 20 sample issues, classify: what kind of issue it is, where to check first, and whether to act / monitor / escalate
• ✓  Build an Issue Classification Reference Card (cheat sheet) for personal use
• ✓  Practice applying the classification to 3 real-looking scenario descriptions

Seller Central Pages, Reports & Tools to Know

• Performance > Account Health
• Catalog > Manage Inventory
• Inventory > Manage FBA Inventory
• Orders > Manage Orders
• Help > Case Log

Common Beginner Mistakes

• ⚠  Treating all issues as listing issues by default — different issue types require different responses
• ⚠  Jumping to a fix before classifying the issue — misdiagnosis causes additional errors
• ⚠  Not distinguishing offer/Buy Box issues from listing/catalog issues

⚠  Treating “I know where this is” as the same thing as “I am authorized to do this” — issue classification should lead to the correct next step, not reckless action

Suggested Mock Exercises / Training Activities

• Issue Classification Drill: 20 scenarios, timed, classify each with correct category and first check
• Reference Card Build: Create a personal Issue Classification Card as a Google Doc or printed cheat sheet
• Peer Scenario Challenge: Pair up, each create 5 scenarios, swap and classify each other's scenarios

Phase 2 — Catalog, Listing & Offer Operations

Module 2.1 — ASIN, SKU, FNSKU, UPC & Variation Fundamentals

Understanding Amazon's product identifier system is essential before touching any listing. Confusing ASIN, SKU, and FNSKU — or misunderstanding parent-child variation relationships — is one of the most common and costly beginner errors.

Learning Objectives

• Define ASIN, SKU, FNSKU, and UPC and explain the role of each
• Distinguish between a parent ASIN and a child ASIN
• Explain what a variation relationship is and how it affects listing display
• Identify whether a product is standalone or part of a variation family
• Explain what a flat file is and why it is sometimes needed

Core Concepts

• ASIN: Amazon Standard Identification Number — Amazon assigns this; unique per product in the catalog
• SKU: Stock Keeping Unit — assigned by the seller; used internally to track inventory and map to ASINs
• FNSKU: Fulfillment Network SKU — used by Amazon's FBA system to track items inside fulfillment centers
• UPC / EAN / GTIN: Product barcodes used to match products to the Amazon catalog
• Parent ASIN: A non-purchasable listing that groups child variations together
• Child ASIN: A purchasable variation — e.g., size Small, color Red
• Variation theme: The attribute used to group variations — e.g., Size, Color, Flavor
• Flat file: An Excel/CSV template used to create or update multiple listings at once — required for bulk operations or specific listing types

Practical Tasks

• ✓  Given a product listing, identify: ASIN, SKU, FNSKU, and whether it has a parent-child relationship
• ✓  Map out a parent-child variation family for a sample product with 3 variants
• ✓  Locate the FNSKU label requirement for an FBA shipment
• ✓  Identify when a flat file would be needed instead of the Seller Central UI

Seller Central Pages, Reports & Tools to Know

• Catalog > Manage Inventory (ASIN and SKU columns)
• Inventory > Manage FBA Inventory (FNSKU visible per unit)
• Catalog > Add Products (ASIN creation or matching)

Common Beginner Mistakes

• ⚠  Using ASIN and SKU interchangeably — they are completely different identifiers
• ⚠  Editing a child ASIN's title or images without understanding the parent-child lock
• ⚠  Creating duplicate ASINs for an existing product instead of matching to the catalog
• ⚠  Confusing FNSKU with SKU when preparing FBA shipment labels

Suggested Mock Exercises / Training Activities

• Identifier Mapping Exercise: Given a Manage Inventory export, create a table mapping SKU → ASIN → FNSKU for 10 products
• Variation Family Map: Given 5 product listings, identify which are parent ASINs and which are children, and map the variation theme
• Flat File Awareness Quiz: Given 5 scenarios, decide: use the Seller Central UI or a flat file?

Listing Issue vs Offer Issue

A beginner must learn early that listing issues and offer issues are not the same thing.

Listing issue = the problem is with the product’s catalog data or listing status. Examples: suppressed listing, missing image, missing attributes, incorrect variation setup, contribution conflict, inactive listing caused by listing quality or compliance issue.

Offer issue = the problem is with the seller’s offer on the listing. Examples: inactive offer, pricing issue, no Buy Box, sellability issue, quantity / fulfillment setup problem.

A listing can be perfectly fine while the offer has a problem. An offer can also be fine while the listing itself is suppressed or broken. A reliable Seller VA must learn to distinguish these before taking action or escalating.

Module 2.2 — Product Detail Page Components & Listing Build Basics

A Seller VA does not need to become a copywriter, but they must understand how a listing is built and which parts commonly cause operational problems. Knowing the components of a listing helps the VA spot missing fields, diagnose suppression reasons, and communicate clearly about listing issues.

Learning Objectives

• Identify the main components of a product detail page
• Understand which listing fields are operationally important
• Know what information is typically needed before creating or updating a listing
• Understand which missing fields often lead to suppression or poor listing quality

Core Concepts

• Title: The main product name — must meet Amazon's character limits and formatting rules
• Bullet points: Key product features shown on the detail page — usually 5 bullets
• Description / A+ Content: Longer product description or enhanced brand content — awareness level for VA
• Images: Main image and additional images — missing main image is a primary suppression cause
• Key attributes: Category-specific required fields — often the source of suppression issues
• Variation attributes: Size, color, flavor, or other variation-defining fields
• Backend / search terms: Hidden keywords in the catalog — not visible to customers but relevant to search
• Browse category / item type: Product classification — must be correct for required attributes to apply
• Brand name consistency: Brand name on the listing must match Brand Registry records to avoid contribution issues

Practical Tasks

• ✓  Audit a sample listing and identify all major components
• ✓  List the minimum information needed before creating or updating a listing
• ✓  Compare a 'healthy' fully-complete listing vs a weak / incomplete listing — note the differences

Seller Central Pages, Reports & Tools to Know

• Catalog > Manage Inventory > Edit Listing (all attribute tabs)
• Catalog > Fix Your Products / Listing Quality Dashboard

Common Beginner Mistakes

• ⚠  Thinking the VA needs to write the content — that's the copywriter's job; the VA monitors and documents
• ⚠  Not knowing what 'required fields' means — these are the fields Amazon requires for a listing to stay active
• ⚠  Confusing A+ Content with regular description — A+ is a brand enhancement tool, not a basic listing field

Suggested Mock Exercises / Training Activities

• Listing Component Audit: Given 3 sample product listings, map all visible components and flag any that appear missing or incomplete
• Minimum Listing Information Checklist: Build a checklist of the minimum fields needed before any listing update
• Healthy vs Weak Listing Comparison: Compare two listings and document the differences in a short report

Module 2.3 — Listing Status, Lifecycle & Suppressed Listings

A listing that is suppressed, inactive, or in error means zero sales for that product. Understanding why listings go inactive — and knowing how to diagnose and escalate the issue — is one of the highest-value skills an Amazon Seller VA can have.

Learning Objectives

• Explain the listing lifecycle from draft to active to inactive or suppressed
• Identify common listing statuses and what each means for sales
• Diagnose the reason a listing is suppressed or inactive
• Know which suppression issues a VA can attempt to resolve and which require escalation
• Document listing issues clearly for handoff

Core Concepts

• Active: Listing is live and purchasable
• Inactive: Listing exists but is not currently available — could be out of stock, suppressed, or stranded
• Suppressed: Amazon has removed the listing from search results due to a data quality or compliance issue
• Common suppression reasons: Missing main image, incomplete required attributes, prohibited keywords, pricing issue, restricted product flag, category approval required
• Contribution conflict: Two sellers or update sources submitting conflicting data for the same ASIN — common cause of listing edits not saving
• Out-of-stock inactivity: Listing goes inactive when FBA stock hits zero — this is different from suppression

Practical Tasks

• ✓  Filter Manage Inventory by 'Inactive' status and classify the reason for each inactive listing
• ✓  Identify a suppressed listing and document the specific suppression reason
• ✓  Attempt to resolve a simulated listing quality alert in the Seller Central UI
• ✓  Write a listing issue log entry: ASIN, issue, evidence, next step
• ✓  Create a suppression triage checklist

Seller Central Pages, Reports & Tools to Know

• Catalog > Manage Inventory (filter by status: Active, Inactive, Suppressed)
• Catalog > Fix Your Products / Listing Quality Dashboard
• Performance > Account Health > Product Policy Compliance
• Catalog > Manage Inventory > Edit (to fix listing attributes)

Common Beginner Mistakes

• ⚠  Assuming 'Inactive' always means suppressed — it can also mean out of stock
• ⚠  Trying to fix suppressed listings without reading the exact suppression reason first
• ⚠  Making listing edits without checking for contribution conflicts first
• ⚠  Not documenting listing issues before attempting a fix

Suggested Mock Exercises / Training Activities

• Suppression Diagnosis Drill: Given a mock Manage Inventory export with 5 inactive listings, classify the reason for each and suggest the next step
• Issue Summary Template Practice: Write 3 listing issue summaries using the standard VA template
• Fix or Escalate? Exercise: Given 8 listing issues, decide which the VA can fix and which require client or specialist action

Module 2.4 — Listing Edits, Flat File Awareness & Contribution Conflicts

Sometimes listing edits save correctly. Sometimes they don't. Sometimes Amazon accepts the update but the detail page doesn't reflect it. A VA must understand the basics of why this happens — and know what to do about it.

Learning Objectives

• Understand the difference between UI edits and flat file updates
• Know when a flat file is likely more appropriate than the UI
• Recognize common reasons listing edits don't reflect on the detail page
• Understand contribution conflicts at a beginner operational level
• Know how to gather evidence before escalating a listing update issue

Core Concepts

• Listing update via UI: Direct edit in Manage Inventory — fast but may be overridden by another data source
• Flat file update: Bulk upload via Excel/CSV — required for some update types; can sometimes override UI edits
• Processing time: Listing updates can take 15 minutes to 24 hours to reflect — this is normal
• Contribution conflict: Competing data sources (seller, Brand Registry, vendor) fighting to control a listing field
• Brand Registry: Gives registered brand owners stronger content control — helps resolve contribution conflicts
• Detail page vs Seller Central: What shows in Seller Central and what appears on the customer-facing detail page may differ temporarily

Practical Tasks

• ✓  Attempt a listing title edit via Seller Central UI and record the outcome
• ✓  Identify whether a listing update issue may be a contribution conflict
• ✓  Download a flat file template for a specific category and identify the key columns
• ✓  Write an escalation note for a simulated contribution conflict issue

Seller Central Pages, Reports & Tools to Know

• Catalog > Manage Inventory > Edit Listing
• Catalog > Add Products via Upload (flat file portal)
• Help > Contact Seller Support (for listing contribution cases)

Common Beginner Mistakes

• ⚠  Submitting the same edit multiple times in frustration — this can create additional conflicts
• ⚠  Assuming the flat file will always win over the UI — it depends on data quality score and Brand Registry status
• ⚠  Not waiting 24 hours before escalating a listing update issue to Amazon
• ⚠  Editing the wrong SKU when a parent has multiple children

Suggested Mock Exercises / Training Activities

• Edit & Monitor Exercise: Submit a sample listing edit, screenshot before and after, and log the result at 1 hour and 24 hours
• Flat File Orientation: Download a flat file for a specific category — identify required fields, image URL field, title field, bullet fields
• Contribution Conflict Scenario: Write an escalation note explaining the issue, evidence gathered, and requested action

Module 2.5 — Offer Health Basics: Price, Buy Box & Sellability Checks

Sometimes the listing itself is fine, but the offer is the problem. A product can be suppressed at the offer level without the catalog listing being suppressed. A Seller VA must know how to recognize when the issue is offer-related — not catalog-related — and flag it correctly.

Learning Objectives

• Understand the difference between a listing issue and an offer issue
• Recognize basic sellability problems related to pricing, Buy Box, inactive offer, or fulfillment setup
• Know when to flag offer-level issues to the client
• Build a simple sellability check checklist

Core Concepts

• Listing vs offer: The listing is the product in Amazon's catalog; the offer is the seller's specific price and fulfillment setup for that listing
• Buy Box: The purchase button on the product page — won based on pricing, fulfillment method, and seller metrics
• No Buy Box: When a seller's offer does not win the Buy Box — the product may be 'live' but not converting
• Inactive offer: The seller's offer is suppressed even if the catalog listing is active — can be caused by pricing, fulfillment setup, or compliance
• FBM shipping template: For FBM offers, an incorrectly set up shipping template can suppress the offer silently
• Price alert: Amazon's automated pricing alerts that flag offers with unusually high or low prices

Practical Tasks

• ✓  Classify 10 sample scenarios: listing issue or offer issue?
• ✓  Build a simple 'Sellability Checklist' covering: listing status, offer status, Buy Box status, pricing, fulfillment setup
• ✓  Write a short client note for a no-Buy-Box scenario or pricing concern

Seller Central Pages, Reports & Tools to Know

• Catalog > Manage Inventory (listing status and offer status columns)
• Pricing > Manage Pricing (price alerts)

Common Beginner Mistakes

• ⚠  Assuming every 'not selling' issue is a listing problem — offer and pricing issues are equally common
• ⚠  Not checking if the offer is actually active when the listing shows 'Active'
• ⚠  Confusing 'winning the Buy Box' with 'being live on Amazon' — a listing can be live but not winning any sales

Suggested Mock Exercises / Training Activities

• Listing vs Offer Classification Drill: Given 10 scenarios, classify as listing issue or offer issue
• Sellability Checklist Build: Create a VA-ready sellability checklist covering all key offer-level checks
• Client Note Writing: Write a brief client update for a no-Buy-Box scenario found during a daily check

Phase 3 — Inventory & Fulfillment Operations

Module 3.1 — FBA vs FBM Operations & Inventory Status

Inventory is the lifeblood of an Amazon business. A VA who understands the operational differences between FBA and FBM — and can correctly read inventory status — can flag risks before they become lost sales.

Learning Objectives

• Explain FBA vs FBM from a VA's operational perspective
• Identify the main inventory status types in Seller Central
• Understand which statuses are normal vs which require investigation
• Explain why available inventory matters more than total inventory

Core Concepts

• FBA: Amazon warehouses the product and ships to customers — VA monitors inventory levels, inbound shipments, and FBA-specific issues
• FBM: Seller ships directly to customers — VA monitors order fulfillment deadlines and seller-fulfilled listings
• Available: Units Amazon can immediately fulfill orders from — the most important number to monitor
• Reserved: Units held for pending orders or in-process shipments — usually normal
• Inbound: Units in a shipment being sent to Amazon's fulfillment centers — not yet sellable
• Unfulfillable: Units Amazon considers unsellable — damaged, expired, or defective
• Stranded: FBA units with no active listing — cannot be sold until the listing issue is resolved
• Reorder point: The inventory level at which restocking should be triggered

Practical Tasks

• ✓  View the FBA Inventory dashboard and record available, reserved, inbound, and unfulfillable counts for 5 SKUs
• ✓  Identify which SKUs are at low-stock or stockout risk based on available units
• ✓  Compare 3 FBA SKUs and 3 FBM SKUs — note differences in VA responsibilities
• ✓  Flag any unfulfillable units and document reason and recommended next step

Seller Central Pages, Reports & Tools to Know

• Inventory > Manage FBA Inventory
• Inventory > Inventory Dashboard
• Inventory > FBA Inventory Health
• Reports > Business Reports (units ordered for velocity context)

Common Beginner Mistakes

• ⚠  Treating 'inbound units' as 'available' — inbound stock is not yet sellable
• ⚠  Ignoring unfulfillable units — they represent money sitting in a warehouse with zero sales potential
• ⚠  Not monitoring FBM orders for late-shipment risk — FBM requires active daily order monitoring

Suggested Mock Exercises / Training Activities

• Inventory Status Classification: Given a mock FBA inventory export, classify each SKU as: healthy / low stock / at-risk / unfulfillable
• VA Inventory Commentary: Write a 5-bullet inventory status summary for a mock account as if sending to a client
• FBA vs FBM Comparison Chart: Fill out a side-by-side VA responsibility comparison table

Module 3.2 — Inventory Health, Low-Stock Monitoring & Restock Awareness

A VA does not need to own the full forecasting model to be useful. They need to know how to identify stock risk clearly and flag it before the listing goes dead. Proactive stock monitoring is one of the most visible ways a VA adds daily value.

Learning Objectives

• Identify low-stock and stockout risk from inventory data
• Understand the purpose of the Restock Report
• Know which inventory numbers matter when flagging risk
• Prepare a basic inventory status summary for a client

Core Concepts

• Days of cover: How many days of sales the current available inventory can support — key metric for restock timing
• Sales velocity: Average units sold per day — use Business Reports for this context
• Restock recommendation: Seller Central's built-in suggestions for when to restock based on sales velocity and lead time
• Stockout risk: When available inventory is critically low relative to daily sales — urgent flag for the client

Practical Tasks

• ✓  Review sample inventory data and identify at-risk SKUs
• ✓  Calculate simple days of cover: available units ÷ average daily sales
• ✓  Prepare a 5-bullet stock risk update for a mock account
• ✓  Compare available units vs recent sales trend in a simple exercise

Seller Central Pages, Reports & Tools to Know

• Inventory > Inventory Planning (Restock tab)
• Inventory > Manage FBA Inventory
• Reports > Business Reports (for sales velocity context)

Common Beginner Mistakes

• ⚠  Relying only on Seller Central's restock recommendations without checking actual recent sales data
• ⚠  Flagging every low-stock SKU without context — include days of cover in every flag
• ⚠  Not distinguishing between slow-selling SKUs that are fine and fast-selling SKUs that are at risk

Suggested Mock Exercises / Training Activities

• Stock Risk Identification: Given a mock inventory export with daily sales data, calculate days of cover for each SKU and flag at-risk ones
• Inventory Update Writing: Write a stock risk alert to a client for a SKU with less than 7 days of cover
• Restock Report Review: Given a mock Restock Report, identify which SKUs need attention within 30 days

Module 3.3 — Stranded Inventory, Inbound Shipment Monitoring & Receiving Discrepancies

Stranded inventory means Amazon has the product in the warehouse but there is no active listing to sell it through — wasted money sitting idle. Inbound shipment delays and receiving discrepancies are common FBA pain points. Proactive monitoring of both is a high-value VA responsibility.

Learning Objectives

• Define stranded inventory and explain why it occurs
• Identify stranded inventory in Seller Central and understand resolution steps by reason
• Explain the stages of an inbound FBA shipment
• Monitor inbound shipment status and flag delays or receiving discrepancies

Core Concepts

• Stranded inventory: FBA units with no matching active listing — at the warehouse but cannot be sold
• Stranded reason types: Listing deleted, listing suppressed, listing closed, ASIN not in catalog — each requires a different resolution
• Inbound shipment stages: Working → Shipped → In Transit → Delivered → Checked In → Receiving → Closed
• Receiving discrepancy: Amazon received a different quantity than what was shipped — VA should flag and open a case if needed
• FC processing time: Amazon can take days or weeks to process a large shipment — normal but requires monitoring

Three Related but Different Workstreams in This Module

A. Stranded Inventory Triage

The VA identifies FBA inventory that cannot be sold because there is no active listing or because a listing-related issue is blocking the inventory from selling.

Typical outputs: identify stranded ASIN / SKU, record stranded reason, suggest the likely resolution path, and log the issue for follow-up.

B. Inbound Shipment Monitoring

The VA monitors the movement and receiving status of FBA shipments after they are sent to Amazon.

Typical outputs: track shipment stage and receiving progress, flag shipments that appear delayed or stuck, compare expected vs. received quantities at a monitoring level, and note which shipments may require follow-up.

C. Receiving Discrepancy Escalation Preparation

The VA prepares the evidence needed when Amazon appears to have received fewer units than expected or when the shipment history needs review.

Typical outputs: gather shipment IDs, quantities, receiving status, and reconciliation evidence; draft a discrepancy summary; update the reimbursement / discrepancy tracker; and escalate the case for review or case creation if needed.

Practical Tasks

• ✓  Locate and export the Stranded Inventory report, identify each ASIN's stranded reason, and draft a resolution plan
• ✓  Open the Manage FBA Shipments queue and track status of 3 inbound shipments
• ✓  Identify any shipments showing receiving delays or quantity discrepancies
• ✓  Update a mock reimbursement / discrepancy tracker with shipment ID, issue type, evidence status, and next step

Seller Central Pages, Reports & Tools to Know

• Inventory > Manage FBA Inventory > Stranded Inventory filter
• Inventory > Manage FBA Shipments (Shipping Queue)
• Reports > Fulfillment Reports > Inventory Reconciliation

Common Beginner Mistakes

• ⚠  Assuming stranded inventory will resolve itself — it requires active action
• ⚠  Not monitoring inbound shipments after sending them — discrepancies can go unnoticed for weeks
• ⚠  Waiting too long to open a receiving discrepancy case — Amazon has time limits on claims

Suggested Mock Exercises / Training Activities

• Stranded Inventory Triage: Given a mock stranded inventory report, classify each ASIN by stranded reason and write the recommended resolution step
• Shipment Tracking Log: Using the Manage FBA Shipments dashboard, fill out a shipment status tracker for 5 shipments
• Restock Readiness Summary: Prepare a mock restock summary showing which SKUs need attention within 30 days

Module 3.4 — Unfulfillable Inventory, Removal Orders & Inventory Cleanup Awareness

Not all inventory problems are about low stock. Sometimes inventory exists but is damaged, unsellable, or costing money to store without any sales potential. Understanding unfulfillable inventory and when removal or disposal may be needed is an important awareness area for a Seller VA.

Learning Objectives

• Understand what unfulfillable inventory is and why it matters
• Recognize when unfulfillable units may need removal or disposal
• Understand removal orders at an awareness level
• Know when to escalate aged or unsellable inventory issues to the client

Core Concepts

• Unfulfillable units: Inventory Amazon considers unsellable — damaged, expired, or defective; still incurs storage fees
• Customer-damaged: Returned by a customer and deemed unsellable by Amazon
• FC-damaged: Damaged while in Amazon's fulfillment center — may be eligible for reimbursement
• Removal order: A request to have Amazon ship FBA inventory back to the seller or dispose of it
• Disposal order: Amazon destroys the units — cheaper than removal if the product has no resale value
• Long-term storage fees: Amazon charges extra fees for inventory stored longer than 181 days — unfulfillable units still count

Practical Tasks

• ✓  Classify sample inventory as sellable, stranded, or unfulfillable
• ✓  Write a short recommendation note for unfulfillable units: quantity, reason, and recommended action (removal / disposal / claim)
• ✓  Identify when a removal-order discussion may be needed based on storage duration and product value

Seller Central Pages, Reports & Tools to Know

• Inventory > Manage FBA Inventory (filter by Unfulfillable)
• Reports > Fulfillment Reports > Inventory Health Report

Common Beginner Mistakes

• ⚠  Ignoring unfulfillable units because they're a small quantity — they still cost storage fees
• ⚠  Assuming all FC-damaged units are automatically reimbursed — this requires monitoring and often a case
• ⚠  Not tracking how long unfulfillable units have been sitting — long-term storage fees apply

Suggested Mock Exercises / Training Activities

• Unfulfillable Inventory Classification: Given a mock inventory report, tag each unfulfillable unit by reason and recommend an action
• Removal vs Disposal Decision Exercise: Given 5 scenarios (product value, quantity, storage duration), decide: remove, dispose, or open a claim
• Client Recommendation Write-Up: Write a short note to a client about unfulfillable units discovered during a weekly inventory review

Phase 4 — Orders, Account Health & Post-Purchase Risk Monitoring

Module 4.1 — Order Issue Awareness, Returns & Refunds Basics

Learning Objectives

• Navigate the Manage Orders dashboard and understand key order statuses
• Identify FBM late-shipment risk and fulfillment deadlines
• Understand returns and refunds basics — when Amazon handles it vs. when the seller must act
• Recognize order metrics that affect Account Health
• Know when to escalate an order issue to the client

Core Concepts

• Order statuses: Pending, Unshipped, Shipped, Delivered, Canceled — each has implications for FBM fulfillment
• Late Shipment Rate (LSR): Percentage of FBM orders shipped after the ship-by date — must stay below 4%
• Order Defect Rate (ODR): Combination of negative feedback rate, A-to-Z claim rate, and chargeback rate — must stay below 1%
• A-to-Z Guarantee Claim: A buyer dispute with Amazon — can damage Account Health and results in automatic refund to buyer
• FBA vs FBM return handling: Amazon handles most FBA returns automatically; FBM returns require active seller response

Practical Tasks

• ✓  Navigate to Manage Orders and identify: pending, unshipped, and late orders
• ✓  Check Account Health for current ODR and LSR metric status
• ✓  Prepare a one-paragraph order health summary for a mock account

Seller Central Pages, Reports & Tools to Know

• Orders > Manage Orders
• Performance > Account Health (ODR, LSR sections)
• Orders > Manage Returns

Common Beginner Mistakes

• ⚠  Thinking FBA orders don't need monitoring — A-to-Z claims and shipment issues still occur in FBA
• ⚠  Confusing A-to-Z claims with negative reviews — they are different and affect Account Health differently
• ⚠  Not knowing the LSR threshold — 4% is the warning level; below this is required to maintain account standing

Suggested Mock Exercises / Training Activities

• Order Health Dashboard Review: Given a mock Manage Orders export, identify all pending, unshipped, and overdue orders
• Metric Risk Assessment: Given Account Health metrics, classify each as healthy / at-risk / urgent
• Order Summary Write-Up: Prepare a one-paragraph order health summary for a mock account

Module 4.2 — Voice of the Customer, Return Reasons & Product/Listing Quality Signals

A good Seller VA does not just see returns as 'orders that came back.' They look for patterns that may signal listing mismatch, product quality issues, packaging problems, or customer expectation gaps. The Voice of the Customer report is one of the most underused but valuable tools in Seller Central.

Learning Objectives

• Understand what Voice of the Customer is for and where to find it
• Identify common return and refund patterns in the VoC report
• Distinguish between possible listing accuracy issues, product quality issues, and fulfillment issues based on return reasons
• Know when recurring post-purchase signals should be escalated to the client

Core Concepts

• Voice of the Customer (VoC): Seller Central dashboard showing buyer feedback and return reasons per ASIN — color-coded by severity
• NCX (Negative Customer Experience): Amazon's measure of how many customers had a poor experience — drives the VoC dashboard
• Listing mismatch: Customer received something different from what was described — listing accuracy issue
• Product quality signal: Multiple customers reporting defects or failures — product issue, not listing issue
• Fulfillment issue: Packaging damage, wrong item sent, late delivery — logistics or prep issue

Practical Tasks

• ✓  Review a mock VoC / return-reason report
• ✓  Identify the top 3 possible root causes behind poor customer experience patterns
• ✓  Classify each issue as: listing accuracy, product quality, or fulfillment problem
• ✓  Write a short escalation note: 'Possible listing mismatch / quality issue — recommend review'

Seller Central Pages, Reports & Tools to Know

• Performance > Voice of the Customer
• Orders > Manage Returns (return reason filter)

Common Beginner Mistakes

• ⚠  Treating all returns as random one-off events — patterns in VoC are signals that need investigation
• ⚠  Not differentiating between listing accuracy and product quality issues — each needs a different response
• ⚠  Escalating every negative customer signal — minor one-off complaints don't always need immediate action

Suggested Mock Exercises / Training Activities

• VoC Pattern Analysis: Given a mock VoC report, identify the top 3 issue categories and write a 3-bullet summary
• Root Cause Classification: Given 10 return reason descriptions, classify each as: listing / product / fulfillment issue
• Escalation Note Practice: Write a client note for a pattern of 'not as described' returns on a specific ASIN

Module 4.3 — Account Health, Policy Warnings & Compliance Risk Awareness

Account Health is one of the most important dashboards in Seller Central. A serious unresolved issue can result in listing removal or account suspension. A VA who monitors this proactively and escalates clearly protects the client's entire revenue stream.

Learning Objectives

• Navigate the Account Health dashboard and understand what each metric means
• Identify the types of policy warnings and compliance violations that appear
• Classify Account Health issues by urgency: immediate escalation, monitor closely, or informational
• Know what a listing removal or account suspension risk looks like
• Write a clear escalation note for an urgent Account Health issue

Core Concepts

• Account Health Rating (AHR): Amazon's overall score of account performance — ranges from 'At Risk' to 'Healthy'
• Policy warnings: Notices from Amazon that a listing or behavior may violate a policy — can lead to removal if unresolved
• Listing deactivation: Amazon removes a specific listing — different from full account suspension
• Account suspension risk: When Account Health deteriorates significantly — the full account may be at risk — immediate escalation required
• Restricted products: Certain products require approval to sell — listing them without approval triggers violations
• Authenticity / IP complaints: Product authenticity or intellectual property complaints — can cause listing removal and serious account health impact
• Response deadline: Many policy warnings have a specific deadline to respond — missing it can accelerate account action

Risk Severity Labels for Seller VA Escalation

Monitor — The issue is worth watching, but does not require immediate action today.

Examples: small VoC signal, isolated return reason, minor listing quality warning with no immediate business impact.

Needs attention this week — The issue should be summarized in the next client update and monitored closely.

Examples: repeated return reasons on one SKU, low stock risk that is not yet critical, a case that needs follow-up soon.

Needs same-day escalation — The client or manager should be informed today because the issue may affect sales, inventory flow, or account performance soon.

Examples: multiple ASINs suddenly suppressed, inbound shipment discrepancy affecting important stock, late shipment risk in an FBM account.

Needs immediate escalation — The issue is urgent and should be escalated as soon as it is discovered.

Examples: account health warning with a deadline, authenticity complaint, policy violation, restricted product issue, or severe account-risk alert.

Practical Tasks

• ✓  Review the Account Health dashboard and list all active warnings and their statuses
• ✓  Classify each warning as: resolve immediately / monitor closely / informational
• ✓  Identify any policy warnings with upcoming response deadlines
• ✓  Draft an escalation note for an urgent Account Health issue using a template
• ✓  Create an Account Health monitoring checklist

Seller Central Pages, Reports & Tools to Know

• Performance > Account Health
• Performance > Account Health > Policy Compliance
• Performance > Account Health > Shipping Performance
• Performance > Account Health > Customer Service Performance

Common Beginner Mistakes

• ⚠  Ignoring policy warnings because the account is still selling — unresolved warnings accumulate and escalate
• ⚠  Not noting response deadlines — missing one can cause automatic listing removal
• ⚠  Trying to resolve complex compliance violations independently — authenticity and IP complaints require client or specialist involvement

Suggested Mock Exercises / Training Activities

• Account Health Triage Drill: Given a mock Account Health dashboard with 6 active issues, classify each and recommend the next action
• Escalation Note Practice: Write client escalation notes for: (a) an authenticity complaint, (b) a late shipment rate warning, (c) a listing deactivation
• Deadline Tracker Exercise: Given 5 Account Health warnings, identify which have response deadlines and build a deadline log

Phase 5 — Seller Support, Reimbursements & Issue Resolution Workflows

Module 5.1 — Seller Support Case Management

Many operational issues cannot be solved inside the dashboard alone. The VA must know when to open a case, how to write it properly, and how to follow through. A well-written case gets faster, more useful responses from Amazon support.

Learning Objectives

• Identify when a support case is needed vs when the issue can be resolved independently
• Know the most common case types a Seller VA handles
• Write a clear, structured, evidence-backed support case
• Follow up effectively when an initial response is unhelpful
• Maintain a case log for all open and resolved cases

Core Concepts

• Case types: Listing issues, inventory discrepancies, account health, payment, shipment receiving, ASIN errors, policy appeals
• Evidence gathering: Screenshots, order IDs, ASIN, SKU, shipment IDs, tracking numbers, timelines — always before opening a case
• Case writing structure: Be specific, be factual, include all relevant IDs, state the exact issue, specify what resolution is needed
• Case follow-up: Amazon cases may close without resolution — re-open with added evidence; escalate channel if needed
• Case log: Running tracker of all open and resolved cases — essential for pattern recognition and client reporting

Support Channel Awareness

Written case / Case Log: Best for documented operational issues, evidence-backed case histories, shipment discrepancies, reimbursement follow-ups, and issues where a written paper trail matters.

Chat / phone support: Sometimes useful for time-sensitive clarification, follow-up, or nudging a stalled case — if the client or workflow allows it.

Client escalation instead of Amazon escalation: Some issues are not primarily an Amazon support problem. If the issue requires a business decision, approval, or brand / compliance judgment, escalate to the client rather than trying to solve it through support.

Practical Tasks

• ✓  Draft a Seller Support case for 3 different scenarios: listing issue, shipment discrepancy, account health clarification
• ✓  Rewrite a vague support case into a strong, structured one
• ✓  Build a case log and maintain it for one week of simulated cases

✓  Given 8 issue scenarios, decide whether the best next step is: open/update written case / use support follow-up / escalate to client

Seller Central Pages, Reports & Tools to Know

• Help > Get Support (case submission portal)
• Help > Case Log (view and manage cases)

Common Beginner Mistakes

• ⚠  Opening a case immediately without gathering evidence first — this leads to slower resolution
• ⚠  Writing vague descriptions like 'my listing is not working' — Amazon needs specific IDs and details
• ⚠  Not following up on stalled cases — Amazon may close cases after inactivity
• ⚠  Not logging cases — losing track of case history makes escalation impossible

Suggested Mock Exercises / Training Activities

• Case Writing Workshop: Given 3 scenarios, write a complete support case for each — peer review for clarity
• Vague to Strong Case Rewrite: Given a poorly written case, rewrite it to be clear, specific, and action-oriented
• Case Log Maintenance Drill: Given a 5-case history, fill out the case log correctly and flag cases needing follow-up

Module 5.2 — Evidence Gathering for Amazon Cases

Weak evidence leads to weak cases. Amazon support responds better when the case is structured clearly and backed by concrete evidence. Knowing what to gather and where to find it before opening a case is a skill that separates an effective VA from an ineffective one.

Learning Objectives

• Identify what evidence is needed for common issue types
• Know where to find relevant IDs, screenshots, dates, shipment references, and report exports
• Organize evidence into a clear case evidence pack before submitting

Core Concepts

• ASINs and SKUs: Required for any listing-related case
• Shipment IDs and tracking numbers: Required for inbound discrepancy and receiving cases
• Screenshots with timestamps: Visual evidence of the issue as it currently appears in Seller Central
• Report exports: Inventory reconciliation, business reports, fulfillment reports — date-stamped exports as evidence
• Case timeline: A brief chronological summary: when the issue started, what was already done, what the current status is

Practical Tasks

• ✓  Build an evidence checklist for each of these case types: suppressed listing, inbound discrepancy, reimbursement issue, stranded inventory
• ✓  Prepare a 'case evidence pack' for a mock shipment discrepancy scenario: shipment ID, units sent, units received, screenshot of receiving summary, reconciliation report export

Seller Central Pages, Reports & Tools to Know

• Inventory > Manage FBA Shipments (shipment ID, receiving summary)
• Reports > Fulfillment Reports > Inventory Reconciliation
• Catalog > Manage Inventory (ASIN, SKU, current status screenshot)

Common Beginner Mistakes

• ⚠  Gathering too much irrelevant evidence — focus on what directly proves the issue
• ⚠  Missing the shipment ID or ASIN — these are non-negotiable for most cases
• ⚠  Not including a timeline — Amazon support needs to understand when the issue started

Suggested Mock Exercises / Training Activities

• Evidence Checklist Exercise: For 4 case types, build a complete evidence checklist showing what to gather and where to find each item
• Mock Evidence Pack: Given a simulated shipment discrepancy, prepare all evidence as if about to submit a case

Module 5.3 — FBA Reimbursements, Lost Inventory & Discrepancy Follow-Up

This is one of the most practical missing pieces in many beginner VA roadmaps. Inventory gets lost, damaged, short-received, or mishandled inside Amazon's fulfillment network. A useful Seller VA should understand how reimbursement-related work begins and how to support the process.

Learning Objectives

• Understand what FBA reimbursement-related issues are
• Recognize the most common reimbursement scenarios
• Understand the basic logic of shipment discrepancy follow-up
• Prepare a discrepancy summary for a case or client review
• Know when to escalate or open a reimbursement-related case

Operational scope for this roadmap: identify shipment and receiving discrepancies, gather the required evidence, maintain a reimbursement tracker, draft case-ready summaries, and follow up on standard reimbursement workflows using the approved process.

Core Concepts

• Inbound shipment short-received: Amazon received fewer units than were sent — may be eligible for reimbursement after investigation
• Units lost in FC: Units show as received but are not reflected in available inventory — case required
• FC-damaged units: Units damaged while in Amazon's warehouse — Amazon may reimburse automatically or after a case
• Returned but not restocked: Customer return received by Amazon but not put back in sellable inventory — requires monitoring
• Reconciliation report: The Inventory Reconciliation report shows what was sent vs. received — foundation for discrepancy cases

Practical Tasks

• ✓  Classify sample reimbursement scenarios by type
• ✓  Prepare a discrepancy summary: shipment ID, units sent, units received, discrepancy quantity, evidence available, requested next step
• ✓  Create a reimbursement tracker template: ASIN, SKU, case type, quantity, case ID, status, resolution

Seller Central Pages, Reports & Tools to Know

• Reports > Fulfillment Reports > Inventory Reconciliation
• Inventory > Manage FBA Shipments (receiving details)
• Help > Get Support (reimbursement case submission)

Common Beginner Mistakes

• ⚠  Assuming all discrepancies will be automatically reimbursed — many require an active case
• ⚠  Not tracking reimbursement cases in a log — these can take weeks to resolve and are easy to lose track of
• ⚠  Opening a reimbursement case too early — Amazon requires a waiting period before some claims are eligible

Suggested Mock Exercises / Training Activities

• Reimbursement Scenario Classification: Given 8 reimbursement scenarios, classify each by type and identify the correct next step
• Discrepancy Summary Write-Up: Given a mock shipment with 50 units sent and 43 received, prepare a complete discrepancy summary
• Reimbursement Tracker Build: Set up a reimbursement tracker template for a mock account

Module 5.4 — Case Follow-Up Discipline, Escalation Paths & Resolution Logging

Learning Objectives

• Know when a case needs follow-up and how to write an effective follow-up message
• Understand when to escalate to a different support channel or to the client
• Document case outcomes and unresolved blockers clearly
• Maintain a complete and accurate case log

Core Concepts

• Case follow-up timing: Follow up within 48–72 hours if no useful response; re-open a closed case if needed
• Escalation channels: Phone support, chat support, or executive escalation — some issues resolve faster via different channels
• Unresolved blocker: A case where Amazon is not moving — document clearly and escalate to client or manager with full case history
• Case log discipline: Every case gets logged: case ID, issue, date opened, current status, last action, resolution — updated every time there is movement

Practical Tasks

• ✓  Maintain a mock case log for one simulated week of 5 cases
• ✓  Review a case history and identify what follow-up should have happened at each stage
• ✓  Write a follow-up message for a stalled case that received an unhelpful initial response
• ✓  Write a client update for an unresolved case that has been open for more than 1 week

Seller Central Pages, Reports & Tools to Know

• Help > Case Log (view and update cases)

Common Beginner Mistakes

• ⚠  Waiting too long to follow up — cases can be auto-closed after inactivity
• ⚠  Sending the same message as a follow-up — add new evidence or reframe the issue in each follow-up
• ⚠  Not logging case updates — history is lost without a log
• ⚠  Escalating to the client before exhausting direct Amazon support options

Suggested Mock Exercises / Training Activities

• Case Log Maintenance Simulation: Manage 5 mock cases over one simulated week — update the log at every stage
• Follow-Up Message Writing: Given a case that received a generic response, write a strong follow-up with additional evidence
• Escalation Decision Exercise: Given 3 stalled cases, decide: follow up again / change support channel / escalate to client — and write the appropriate message

Phase 6 — Reporting, Communication & Documentation

Module 6.1 — Reading Operational Reports & Dashboards

A VA who can only click around but cannot read a report is only half useful. Reading and interpreting reports is what separates a data-aware VA from one who just follows instructions. This skill enables faster issue identification and better client communication.

Learning Objectives

• Identify which Seller Central report answers which operational question
• Know what the common operational reports are for
• Extract relevant data from reports and summarize findings
• Identify anomalies and patterns in report data

Core Concepts

• Business Reports (Detail Page Sales): Sessions, units ordered, unit session percentage — for sales performance monitoring
• Inventory Health Report: Available, reserved, unfulfillable, and stranded inventory by SKU
• FBA Restock Report: Recommended restock quantities and timing based on sales velocity
• Inventory Reconciliation Report: What was sent to Amazon vs what was received — for shipment discrepancy cases
• Stranded Inventory Report: All FBA units without an active listing
• Account Health Dashboard: All performance metrics, policy warnings, and compliance issues
• Voice of the Customer: Buyer feedback signals and return/refund reasons per ASIN
• Manage Orders Export: Full order data including status, ship-by dates

Practical Tasks

• ✓  Report Matching: Given 10 operational questions, identify which report answers each
• ✓  Data Extraction: Given a mock Business Report export, fill out a summary table with key metrics per ASIN
• ✓  Anomaly Identification: Given a month of Business Report data with a planted drop in sessions, identify and explain it

Seller Central Pages, Reports & Tools to Know

• Reports > Business Reports > Detail Page Sales and Traffic
• Reports > Fulfillment Reports (Inventory Health, Reconciliation, Stranded)
• Inventory > Inventory Planning (Restock Report)
• Performance > Account Health
• Performance > Voice of the Customer

Common Beginner Mistakes

• ⚠  Reading numbers in isolation without context — a session drop means nothing without knowing if there was a listing edit or price change
• ⚠  Exporting reports without a clear objective — set a question before downloading any report
• ⚠  Not dating reports — always note when a report was pulled

Suggested Mock Exercises / Training Activities

• Report Matching Exercise: 10 operational questions, match each to the correct report
• Data Extraction Drill: Given a mock Business Report, fill out a VA summary table with key metrics per ASIN
• Anomaly Identification: Given a month of data with a planted anomaly, identify and write a 2-sentence explanation

Module 6.2 — Daily Summaries, Weekly Reports & Client Updates

Clients don't just need data — they need a useful update they can understand quickly. A VA who can produce a concise, well-structured daily summary and weekly report is far more valuable than one who sends walls of raw data.

Learning Objectives

• Write concise, clear daily account check summaries
• Prepare a simple weekly operations summary
• Structure updates around: issue, evidence, impact, next step
• Avoid vague or noisy reporting that buries the important information

Core Concepts

• Daily summary: What was checked, what was found, what was done — kept to 3–5 bullet points
• Weekly operations report: A higher-level summary of the week: listing status, inventory health, account health, cases, notable events
• Update structure: Issue → Evidence → Impact → Action Taken → Recommended Next Step → What Needs Approval
• Signal vs noise: Only include information the client needs to know or act on — everything else stays in the log

Recommended Weekly Operations Report Structure

Probinsiyanong VA Weekly Ops Report

1. Account snapshot — brief summary of the account’s current operational state

2. What was checked / completed this week — recurring workflows completed, major reviews done

3. Issues found — listing, inventory, order, account health, case, or VoC issues

4. Evidence / data — key numbers, affected SKUs / ASINs, report findings, case IDs, shipment IDs

5. Actions taken — what was already done by the VA

6. Items needing approval / escalation — issues the client or manager needs to decide on

7. Open cases / follow-ups — unresolved items still in motion

8. Watchlist for next week — stock risks, case follow-ups, listing issues, account-health concerns to monitor

Practical Tasks

• ✓  Write a 3-line daily account summary for 3 different mock account states
• ✓  Write a 5-bullet weekly operations update
• ✓  Write a stock risk alert to a client
• ✓  Write a listing issue summary with recommended action

Seller Central Pages, Reports & Tools to Know

• Probinsiyanong VA Daily Summary Template
• Weekly Report Template

Common Beginner Mistakes

• ⚠  Writing reports that are too long — clients do not have time to read walls of text
• ⚠  Using jargon without explanation — not all clients are Amazon experts
• ⚠  Reporting everything at the same urgency level — urgent issues get buried
• ⚠  Sending updates without recommending an action — clients want to know what to do, not just what happened

Suggested Mock Exercises / Training Activities

• Daily Summary Writing Practice: Write 3 daily summaries for mock accounts with different issue types
• Weekly Report Write-Up: Using a mock 5-day log, write a complete weekly operations summary
• Urgency Sorting: Given 10 findings, sort them into: report immediately / include in daily update / log only

Module 6.3 — Issue Summaries, Escalation Notes & Professional Written Communication

A VA who cannot communicate clearly becomes a liability. The goal is not 'mahaba magsulat.' The goal is 'malinaw, complete, at useful.' This module trains the communication discipline that makes a VA trustworthy.

Learning Objectives

• Write issue summaries with proper structure
• Communicate with clients professionally without sounding robotic
• Distinguish between an FYI update and an action-needed escalation
• Document what happened, what was checked, what was found, and what is recommended

Core Concepts

• Issue summary structure: Issue → Evidence → Impact → Action Taken → Recommended Next Step → What Needs Approval (if any)
• FYI vs escalation: FYI: the client should know this, but no action needed now. Escalation: the client must decide or act now.
• Professional tone: Clear, factual, brief — no panic language, no over-explanation, no unnecessary jargon
• WhatsApp / ClickUp / email formatting: Different channels have different formatting norms — know how to adapt

Practical Tasks

• ✓  Rewrite 3 poor client updates into clear, professional ones
• ✓  Write escalation notes for: repeated listing suppression, stockout risk, shipment discrepancy, account health warning
• ✓  Write a WhatsApp-style escalation message that is under 10 lines but complete

Seller Central Pages, Reports & Tools to Know

• Probinsiyanong VA Issue Summary Template
• Escalation Note Template

Common Beginner Mistakes

• ⚠  Sending updates that begin with 'Hi!' and bury the issue at the bottom — lead with the finding
• ⚠  Writing vague updates like 'may issue sa listing' — always include ASIN, reason, and recommended action
• ⚠  Not distinguishing between FYI and escalation — both get the same urgency from the client

Suggested Mock Exercises / Training Activities

• Issue Summary Peer Review: Write an issue summary, exchange with a classmate, and provide written feedback
• Poor-to-Good Rewrite: Given 5 weak client updates, rewrite each using the standard structure
• Escalation Note Speed Drill: Write an escalation note for an Account Health warning in under 5 minutes

Module 6.4 — Logs, Trackers & Documentation Discipline

If it isn't documented, it's easy to forget, miss, or repeat. Documentation is one of the things that separates a casual VA from an operations-minded VA. Good documentation also allows for smooth handoffs, training of others, and identification of recurring problems.

Learning Objectives

• Maintain a daily task log using a standardized format
• Build and use a case log, listing issue tracker, inventory risk tracker, and reimbursement tracker
• Understand the purpose of each tracker and what belongs in it
• Develop the habit of logging findings immediately, not from memory

Core Concepts

• Daily Check Log: What was checked, what was found, what was done — one entry per day
• Listing Issue Tracker: All known listing problems, their current status, and next steps
• Inventory Risk Tracker: SKUs flagged for low stock, stranded, or unfulfillable status — updated weekly
• Case Log: All open and resolved Seller Support cases with IDs, dates, status, and resolution
• Reimbursement Tracker: All reimbursement-related cases with quantity, case ID, status, and resolution
• Weekly Operations Summary Sheet: A rollup of the week's logs into a client-ready summary

Practical Tasks

• ✓  Set up all 5 core trackers from scratch using templates
• ✓  Maintain all trackers for one simulated week of mock account activity
• ✓  Prepare a weekly summary report from a completed week of logs
• ✓  Identify missing documentation in a 'messy mock account' scenario

Seller Central Pages, Reports & Tools to Know

• Google Sheets (all tracker templates)
• ClickUp or Notion (if used by client)
• Probinsiyanong VA Tracker Pack

Common Beginner Mistakes

• ⚠  Updating trackers from memory at the end of the day — log immediately to prevent errors
• ⚠  Keeping trackers private — all logs should be accessible to the client or manager at any time
• ⚠  Creating overly complex trackers that are hard to maintain — simple and consistent is better
• ⚠  Not dating entries — undated entries have no useful context

Suggested Mock Exercises / Training Activities

• Tracker Setup Workshop: Build all 5 core trackers from the provided template structure
• 5-Day Documentation Challenge: Simulate 5 workdays and maintain all trackers throughout
• Messy Account Audit: Given an account history with missing documentation, identify what was not logged and what the gaps could have caused

Phase 7 — SOPs, Recurring Workflow Management & Process Ownership

Module 7.1 — SOP Writing for Amazon Seller VA Work

If a task repeats, it should eventually become SOP-worthy. SOPs reduce mistakes, improve consistency, enable handoffs, and help the VA scale beyond memory. Writing a clear, usable SOP is a skill that signals professional maturity.

Learning Objectives

• Define what a good SOP is and why it matters
• Identify which Amazon VA tasks are SOP-worthy
• Write a step-by-step SOP for a recurring VA task
• Build a daily-use checklist from an existing SOP
• Evaluate whether an SOP is complete and usable by someone with no prior context

Core Concepts

• SOP: A written, step-by-step guide for completing a recurring task — includes purpose, steps, tools, expected output, and escalation points
• Checklist: A simplified SOP used during task execution — lists what to check or do in order
• Handoff-readiness: An SOP is handoff-ready if someone unfamiliar with the account could complete the task using only the SOP
• Living document: SOPs must be updated whenever a process changes — outdated SOPs create errors

Practical Tasks

• ✓  Write a complete SOP for the Daily Account Check Routine
• ✓  Write an SOP for the Suppressed Listing Triage Process
• ✓  Write an SOP for the Seller Support Case Workflow
• ✓  Convert each SOP into a daily-use checklist
• ✓  Peer-audit a classmate's SOP for clarity, completeness, and handoff-readiness

Seller Central Pages, Reports & Tools to Know

• Google Docs (SOP writing)
• Google Sheets (checklist format)
• Probinsiyanong VA SOP Template

Common Beginner Mistakes

• ⚠  Writing SOPs that assume too much prior knowledge — the reader may be a complete beginner
• ⚠  Making SOPs too long — clarity matters more than comprehensiveness
• ⚠  Not including escalation points — an SOP must say what to do when something goes wrong
• ⚠  Writing the SOP once and never updating it

Suggested Mock Exercises / Training Activities

• SOP Writing Workshop: Write SOPs for 2 of the following — Daily Account Check, Suppressed Listing Triage, Weekly Inventory Review, Support Case Workflow
• SOP Peer Audit: Complete a classmate's task using only their SOP and note any gaps
• Checklist Sprint: Convert 3 completed SOPs into daily-use checklists

Module 7.2 — Recurring Workflow Management

A process owner does not just do tasks — they manage a rhythm. Recurring workflow management means knowing what needs to happen, on what schedule, producing what output, and what to do when it doesn't go as expected.

Learning Objectives

• Define recurring workflow and its components: trigger, steps, tools, output, escalation points
• Map a recurring workflow from start to finish
• Maintain a recurring cadence without being told every time
• Know the suggested recurring workflows for an Amazon Seller VA

Core Concepts

• Daily account check: Every workday — listing status, inventory alerts, account health, open cases, order risk
• Weekly listing health sweep: Every week — review all listings for status changes, new suppression issues, contribution conflicts
• Weekly inventory and restock review: Every week — check available units, days of cover, stranded, unfulfillable, and inbound status
• Case follow-up review: Every 2–3 days — check all open cases for responses, follow up on stalled cases
• Weekly account health / VoC review: Every week — check Account Health metrics, new policy warnings, VoC signals
• Reimbursement follow-up queue: Every week — check status of open reimbursement cases and update tracker

Practical Tasks

• ✓  Map the Weekly Inventory Review workflow from trigger to completion
• ✓  Set up a recurring workflow tracker showing all 6 workflows, their frequency, and last completion date
• ✓  Manage a simulated weekly operations rhythm across all 6 workflows for one week

Seller Central Pages, Reports & Tools to Know

• Google Sheets (Recurring Workflow Tracker)
• Probinsiyanong VA Workflow Map Template

Common Beginner Mistakes

• ⚠  Waiting to be assigned each task every time — a process owner proactively runs the workflow on schedule
• ⚠  Missing a weekly review because 'nothing seemed urgent' — the value of the review is catching issues before they become urgent
• ⚠  Running workflows but not documenting outputs — the output of every workflow should be logged

Suggested Mock Exercises / Training Activities

• Workflow Mapping Exercise: Map the Weekly Inventory Review — include trigger, steps, tools, expected output, and escalation points
• Recurring Workflow Tracker Setup: Build a tracker for all 6 workflows with frequency and last-completed date
• One-Week Operations Simulation: Run all 6 workflows across a simulated week and submit completed logs

Module 7.3 — Root-Cause Thinking & Process Improvement

If the same issue keeps happening, a process owner must stop treating it as a one-time problem and start asking why it keeps recurring. Root-cause thinking is what separates a reactive VA from a proactive one.

Learning Objectives

• Distinguish a one-off issue from a recurring process problem
• Apply a simple root-cause method (5-Why) to common Amazon VA issues
• Identify patterns across repeated listing, inventory, or case issues
• Recommend a process improvement or escalation path based on root-cause findings

Core Concepts

• 5-Why method: Ask 'why?' five times to trace a symptom back to its root cause — prevents treating symptoms instead of causes
• Pattern recognition: When the same issue type recurs 3+ times, it is a process problem — not a coincidence
• Process improvement: Identifying inefficiencies, recurring errors, or missing steps in a workflow — and proposing or implementing a fix
• Process improvement log: A record of identified patterns, root causes, proposed fixes, and their outcomes

Practical Tasks

• ✓  Apply 5-Why analysis to: recurring listing suppression, repeated shipment discrepancies, recurring account health warnings
• ✓  Build a simple process improvement log for a mock account
• ✓  Write a root-cause summary for a recurring issue and recommend a fix

Seller Central Pages, Reports & Tools to Know

• Google Docs (5-Why Template)
• Probinsiyanong VA Process Improvement Log Template

Common Beginner Mistakes

• ⚠  Fixing the symptom every time without asking why it keeps happening
• ⚠  Escalating a recurring issue as if it is new each time — pattern recognition is part of the VA's job
• ⚠  Overcomplicating root-cause analysis — the 5-Why method is enough for most operational VA issues

Suggested Mock Exercises / Training Activities

• 5-Why Drill: Apply the 5-Why technique to 3 recurring Amazon VA scenarios
• Pattern Identification: Given a 4-week issue log, identify which issues are recurring and which are one-off
• Process Improvement Proposal: Write a one-paragraph process improvement recommendation for a recurring listing suppression pattern

Module 7.4 — Handoff Readiness & Process Owner Final Simulation

The final proof of readiness is whether the trainee can manage a recurring workflow end-to-end, document it completely, and hand it off to another person if needed — without the next person needing to ask clarifying questions.

Learning Objectives

• Run a full recurring workflow end-to-end with complete documentation
• Maintain all required logs and trackers to a client-ready standard
• Document exceptions and next steps clearly for handoff
• Produce a process owner summary that another VA could use to continue the work

Core Concepts

• Handoff document: A summary of the current state of all workflows — what is running, what is pending, what needs attention, and what needs to be picked up
• Process owner summary: A brief document showing: which workflows the VA owns, current status of each, open issues, and recommended next actions
• Client-ready standard: Documentation and communication that the client can read, understand, and act on without needing to ask follow-up questions

Practical Tasks

• ✓  Manage a mock account workflow for 1–2 weeks using all checklists, SOPs, and logs
• ✓  Submit a complete Process Owner Summary Package including: Daily Check Logs, Issue Tracker, Case Log, Inventory Risk Summary, Weekly Report, 1 SOP, 1 Root-Cause Analysis, and Final Handoff Summary

Seller Central Pages, Reports & Tools to Know

• All tools and templates from Phases 1–7

Common Beginner Mistakes

• ⚠  Producing a handoff document that only makes sense to the person who wrote it — it must be self-explanatory
• ⚠  Treating the final simulation as a test to pass rather than a rehearsal for real work
• ⚠  Submitting incomplete documentation — all 7 components of the final package are required

Suggested Mock Exercises / Training Activities

• 1-Week Process Owner Simulation: Manage a mock account using all Probinsiyanong VA templates for 5 consecutive simulated workdays
• Final Submission Review: Peer-review another trainee's Process Owner Summary Package and give structured feedback
• Community Showcase: Present your final simulation outputs in the Probinsiyanong VA Facebook group as your graduation project

7. Recommended Training Deliverables Per Phase

Each phase should produce concrete training deliverables — worksheets, templates, exercises, or simulations that can be used in the Facebook group, video lessons, or practicum sessions.

8. Recommended Teaching Format for the Facebook Group

Because this program runs inside the Probinsiyanong VA community rather than a corporate LMS, the lesson format should be practical, community-friendly, and easy to follow on mobile.

Per-Module Lesson Structure

Each module should follow this sequence — whether delivered as a Facebook post, a video lesson, or a live session:

Recommended Weekly Training Flow

To keep the pace manageable without losing momentum, use this weekly rhythm per module:

• Day 1: Concept lesson or video — explain the 'why' and the key concepts
• Day 2: Demo or walkthrough — show where this lives in Seller Central and what it looks like
• Day 3: Worksheet or exercise — trainee works through the task with a template
• Day 4: Scenario or case study — apply the concept to a realistic situation
• Day 5: Summary, quiz, or submission — review, consolidate, and submit output

Mobile-First Delivery Notes

Because many learners will consume lessons inside Facebook on mobile, lesson delivery should stay scannable and action-oriented.

Prefer short concept posts over giant text walls

Use screenshots, checklists, mini-scenarios, and sample updates whenever possible

End each lesson with a concrete output: a short answer, worksheet, tracker entry, issue summary, or discussion response

Use longer reference documents only when they support a clear task or downloadable template

9. What a Job-Ready Graduate of This Roadmap Should Be Able to Do

Seller Central Operations

• ✓  Navigate Seller Central confidently and consistently
• ✓  Complete a structured daily account check efficiently using a checklist and produce a clear written summary of findings, actions taken, and escalation items
• ✓  Identify listing, inventory, order, and account health issues
• ✓  Document findings clearly in a log
• ✓  Distinguish what they can act on vs what needs escalation

Catalog & Listing Work

• ✓  Identify ASIN, SKU, FNSKU, and parent-child variation relationships
• ✓  Recognize suppressed and inactive listing issues and classify the cause
• ✓  Document listing problems clearly with ASIN, reason, evidence, and next step
• ✓  Understand listing edit issues and contribution conflict basics
• ✓  Recognize basic offer health issues: pricing problems, no Buy Box, inactive offer

Inventory & Fulfillment Work

• ✓  Read FBA inventory status correctly: available, reserved, inbound, unfulfillable, stranded
• ✓  Identify stock risk, calculate basic days of cover, and prepare a restock summary
• ✓  Monitor stranded inventory and inbound shipment status
• ✓  Recognize unfulfillable inventory situations and recommend removal / disposal / claim
• ✓  Support standard FBA reimbursement and receiving discrepancy workflows by identifying issues, gathering evidence, maintaining the tracker, drafting case-ready summaries, and following up using the approved process

Order & Account Health Monitoring

• ✓  Identify order-related fulfillment risks for FBM accounts
• ✓  Read Voice of the Customer signals and identify return reason patterns
• ✓  Recognize account health warnings and policy compliance risks
• ✓  Escalate urgent account issues responsibly with a clear written summary

Seller Support & Issue Resolution

• ✓  Write clear, evidence-backed Seller Support cases
• ✓  Gather the correct evidence before opening any case
• ✓  Follow up on cases, maintain a case log, and escalate stalled cases appropriately
• ✓  Support standard FBA reimbursement and receiving discrepancy workflows at an operations level using the approved process

Reporting & Communication

• ✓  Write daily account check summaries and weekly operations reports
• ✓  Summarize issues with the structure: Issue → Evidence → Impact → Action → Next Step
• ✓  Maintain daily logs, listing trackers, inventory trackers, case logs, and reimbursement trackers
• ✓  Communicate clearly and professionally via WhatsApp, ClickUp, or email

Process Ownership

• ✓  Write SOPs for recurring Amazon Seller VA tasks
• ✓  Manage assigned recurring workflows independently using SOPs, trackers, and escalation rules while keeping outputs documented and handoff-ready
• ✓  Identify recurring problems and investigate root causes using the 5-Why method
• ✓  Produce complete, handoff-ready documentation at any point
• ✓  Run a full operations workflow and submit a Process Owner Summary Package