Search by Task or Error
Use the words the user sees or says when something goes wrong.
- “Scan item QR”
- “Move item to new rack”
- “Outbound item missing”
- Known validation/error text where useful
Resources · Help Center
Find the Exact Task, Follow the Current Procedure and Resolve Common Problems before Opening a Support Case
Search by task, workflow stage, screen, role or known error; open one maintained article; confirm prerequisites; follow the exact steps; verify the expected result; recover from common failures; and escalate with context only when self-service is not enough.
Help Center is the task-resolution layer for Seller Central. It is different from Seller Academy, which teaches concepts and complete learning paths, and different from Support Central, which handles account-specific investigation, incidents and issues that require intervention.
From “How do I?” to a verified result
Find + prepare + do + verify + recover
Find + prepare + do + verify + recover
01
Find the Task
Search using the terms users recognise: task, screen, workflow stage, role, item state or known error text.
Find the Task
Search using the terms users recognise: task, screen, workflow stage, role, item state or known error text.
→
02
Prepare and Execute
Confirm prerequisites and permissions, then follow the maintained steps in the same sequence as the actual workflow.
Prepare and Execute
Confirm prerequisites and permissions, then follow the maintained steps in the same sequence as the actual workflow.
03
Verify and Recover
Check the expected result, then use the documented recovery or exception path if the normal workflow does not complete.
Verify and Recover
Check the expected result, then use the documented recovery or exception path if the normal workflow does not complete.
04
Escalate with Context
If the issue needs investigation or intervention, open Support Central with the article, workflow and safe task/reference context preserved.
Escalate with Context
If the issue needs investigation or intervention, open Support Central with the article, workflow and safe task/reference context preserved.
One task should have one canonical maintained procedure. Search results, contextual help, FAQs and Academy lessons should point users to that same source.
One task · one maintained answer
One task · one maintained answer
Find help in the way the user thinks about the problem
Search by Task, Browse by Journey or Open Contextual Help from the Screen
Users should not need to know the name of a WordPress plugin, PHP class or database table to find help. The entry point should match the work they are actually trying to complete.
↔ Swipe through Help Center entry points
Browse by Journey or Role
Navigate through the same operating areas users already recognise in Seller Central.
- Onboarding
- Receive / Store / Fulfil
- Publishing / Marketplaces
- Commerce OS / Administration
Open Contextual Help
Link directly from the screen, validation state or exception where the question occurs.
- Complex control help
- Error-to-troubleshooting link
- Related Operational Guide
- Support escalation if unresolved
Four connected Help Center components
Find the Right Article, Follow the Procedure, Recover from Exceptions and Escalate Only when Needed
Good help content answers four questions in order: Is this the right article? Am I ready to start? What exactly do I do? What should I do if the expected result does not happen?
↔ Swipe through the Help Center components
Search & Information Architecture
Organise help by task, stage, role, screen and operating area with useful synonyms and current-content signals.
SearchFilterBrowseCurrent
Task Article Structure
Give the user prerequisites, exact steps, screenshots where useful, expected result and related next action.
PrerequisiteStepsResultNext
Troubleshooting & Exceptions
Explain common failure states, safe recovery, when unaffected work may continue and when the user must stop.
ErrorRecoverExceptionStop/Continue
Escalation & Content Governance
Send unresolved cases to Support Central with context and keep the article itself current, owned and clearly superseded when retired.
EscalateOwnerReviewSupersede
See the Help Center task-resolution flow in action
Follow a User from Search through the Canonical Task Article, Troubleshooting and Context-Preserving Support Escalation
Start with the complete Help Center architecture, then move through task search, filters, article structure, prerequisites, execution, expected results, recovery, contextual help, Support Central escalation and content governance.
↔ Swipe through the Help Center walkthrough
01
Make the right current article easier to find than an old or irrelevant one
Make the right current article easier to find than an old or irrelevant one
Task Language, Synonyms, Workflow Stage, Role, Operating Model, Screen Context and Current/Superseded State
Search quality depends on the vocabulary users recognise. “QR not scanning”, “wrong item picked”, “move rack”, “publish draft” and “return not available” can all be better entry terms than internal architecture names.
Search and browse should also suppress stale guidance. A superseded article may retain historical value, but it should not outrank the current maintained procedure.
User vocabulary over internal jargonCurrent content ranked firstRole, stage and screen context as filters
↔ Swipe through Help Center search controls
Task & Error Search
Index the phrases users actually type when completing or troubleshooting work.
- Task names
- Screen labels
- Known error text where useful
- Synonyms and alternate phrasing
Browse by Operating Area
Use the same information architecture users already see across Seller Central.
- How It Works stage
- Service / marketplace / Commerce OS area
- Role
- Operating model where relevant
Article Signals
Help the user judge whether the result is applicable before opening it.
- Task/article title
- Applies-to role/scope
- Last reviewed date where useful
- Current / superseded status
Search Result Priority
Prefer canonical current guidance over duplicates and historical copies.
- Current procedure first
- Duplicate content consolidated
- Superseded content demoted
- Replacement link visible
02
Tell the user whether they are ready before telling them where to click
Tell the user whether they are ready before telling them where to click
Purpose, Applies-To Scope, Prerequisites, Permissions, Exact Steps, Evidence, Expected Result and Related Next Action
A task article should be executable without forcing the user to infer missing prerequisites. If a warehouse operator must have a locked task, a specific location state or an approved reservation before scanning, say so before Step 1.
Steps should follow the actual screen and physical sequence. For high-volume workflows, keep the instructions concise enough that the operator can refer to them without slowing down the work.
Prerequisites before Step 1Steps aligned to real screen orderExpected result and next state explicit
↔ Swipe through task-article structure
Purpose & Applies To
Confirm the article is for the right task, role and operating context.
- What this task accomplishes
- Applicable user/role
- Applicable operating model/site where relevant
- Related state or workflow stage
Prerequisites & Permissions
State what must already be true before the user starts.
- Required status/state
- Required access/permission
- Required item/task/reference
- Required physical material or evidence
Exact Steps
Mirror the actual interaction and physical sequence.
- Short numbered actions
- Current control labels
- Screenshot only where it adds value
- Do not hide critical steps in images
Expected Result & Next Action
Tell the user how to confirm success and what should happen next.
- Expected status/state
- Confirmation/evidence
- Next workflow step
- Troubleshooting link if result differs
03
Troubleshooting should protect inventory truth, not merely get the user past an error
Troubleshooting should protect inventory truth, not merely get the user past an error
Recognise the Failure, Preserve the Current State, Try Safe Recovery, Route Exceptions and Know when to Stop
A useful troubleshooting article explains what the error means operationally. If the system cannot verify an item, the answer should not simply tell the user to bypass verification; it should explain whether the item must remain unverified, held or routed to an exception.
Where a failure affects only one row or item, unaffected work may continue if the workflow safely supports it. Where continuing could corrupt custody, availability or approval state, the guide should explicitly tell the user to stop and escalate.
Preserve state before retrySafe retry versus controlled exceptionExplicit stop/continue guidance
↔ Swipe through troubleshooting and exception controls
Identify the Failure
Connect the visible symptom to the workflow state it may affect.
- Error/validation text
- Current item/task state
- Affected versus unaffected work
- Likely recoverable versus investigation needed
Safe Recovery
Provide only recovery steps that preserve the accountable record.
- Retry/reload/re-scan where safe
- Re-authenticate/reconnect where applicable
- Re-open current task/state
- Never suggest silent data overwrite as a shortcut
Exception Path
Route the item/task when normal processing cannot continue.
- Hold / shortage / discrepancy
- Owner or supervisor
- Evidence/reference
- Continue unaffected work where safe
Stop and Escalate
Make the escalation boundary explicit when continuing could create incorrect custody or commercial state.
- Do not force completion
- Preserve current status
- Capture safe diagnostic context
- Open Support Central
04
Escalation should carry context forward; content governance should prevent the same problem from recurring through stale guidance
Escalation should carry context forward; content governance should prevent the same problem from recurring through stale guidance
Support Handoff, Safe References, Article Ownership, Review Dates, Release Impact, Superseded Content and Feedback Loops
When self-service does not resolve the problem, the escalation should include the task/article context and safe identifiers already available to the system. Users should not have to rewrite the entire history or expose passwords, secret keys or unrelated personal data.
Help Center content itself needs maintenance. Product changes, workflow changes and recurring support cases should trigger article review so users are not repeatedly sent into an outdated recovery path.
Support case with preserved contextSafe references, never secretsRecurring support issue feeds documentation improvement
↔ Swipe through escalation and article-governance controls
Support Handoff
Carry the useful task context into Support Central.
- Article/task being followed
- Safe request/item/task ID
- Current state/error summary
- Evidence/attachment path
Safe Diagnostic Context
Collect only what support needs to investigate the issue.
- No passwords or secret keys
- No unnecessary KYC/bank data
- Sanitised screenshots where useful
- Environment/module/reference IDs
Article Governance
Keep each maintained task article tied to an accountable owner and review state.
- Owner/team
- Last reviewed date
- Applies-to scope/version where useful
- Current / superseded / replacement state
Feedback Loop
Use recurring confusion and support cases to improve the canonical article.
- Search-with-no-result patterns
- Repeated support issue
- Release/process change
- Article update and stale-copy retirement
Help Center task-resolution workflow
Find, Confirm, Prepare, Execute, Verify and Recover—or Escalate
The workflow should make self-service fast without encouraging users to bypass the controls that protect inventory, custody and commercial state.
↔ Swipe through the Help Center workflow
Find
Search or browse using the task, stage, role, screen or error the user recognises.
Confirm
Check that the article applies to the current role, operating context and workflow state.
Prepare
Confirm prerequisites, permissions, required references and physical evidence before Step 1.
Execute
Follow the maintained steps in the same order as the actual screen and physical process.
Verify
Confirm the expected result, status, evidence and next workflow state.
Recover or Escalate
Use safe troubleshooting first; if investigation is required, open Support Central with context preserved.
Help Center is not Seller Academy
Academy builds understanding and learning paths. Help Center is for completing or troubleshooting a concrete task.
Help Center is not Support Central
Reusable task guidance belongs here. Account-specific incidents, bugs and investigation requiring intervention belong in Support Central.
Help Center ownership
Operations Own Process Accuracy; Product Teams Own System Behavior; Resources Own Findability and Maintenance
Every important task article should have a route back to the people who can confirm whether the operating process or the software behavior changed.
Help Area
Operations / Subject Owner
Product / Technology
Resources / Support
Task purpose and operating sequence
Own process truth
Confirm system sequence
Publish clear article
Screen labels and system behavior
Validate operational use
Own product behavior
Keep article current
Troubleshooting and safe recovery
Validate operational consequence
Confirm technical recovery boundary
Structure recovery/escalation path
Support escalation
Provide operational evidence
Investigate product issue where needed
Support Central owns case routing
Article lifecycle
Confirm process still applies
Confirm release/version effect
Review, supersede, replace and improve search
↔ Swipe through Help Center ownership views
Operations / Subject Owner
- Task purpose Own
- Process sequence Own
- Exceptions Validate
- Operating change Review
Product / Technology
- System behavior Own
- Screen state Confirm
- Error/recovery Confirm
- Release impact Provide
Resources / Support
- Search/findability Own
- Article structure Maintain
- Support escalation Route
- Stale content Retire
Recommended Help Center categories
Browse by the Operating Areas Users Already Recognise
The category structure should mirror the live operating environment rather than creating a separate documentation-only taxonomy.
↔ Swipe through recommended Help Center categories
Help Center FAQs
Common Questions about Task Help and Troubleshooting
Help Center should make routine work self-service while preserving Support Central for issues that truly need investigation or intervention.
What is Help Center for?
Task-level guidance and troubleshooting for using Seller Central, managed workflows and supported Commerce OS operations.
How is Help Center different from Seller Academy?
Seller Academy teaches concepts and learning paths. Help Center helps the user complete or troubleshoot a specific live task.
How is Help Center different from Operational Guides?
Help Center is broader task and troubleshooting documentation. Operational Guides are more formal repeated procedures, SOPs and checklists for operational execution.
Should an article include prerequisites?
Yes when the task depends on a prior state, permission, task lock, reservation, physical material or other condition that must be true before Step 1.
Can Help Center articles include screenshots?
Yes, when a screenshot materially clarifies the task. Critical instructions should still remain in accessible text and screenshots should use sanitised or fictional data where required.
What should happen if the normal workflow fails?
The article should explain safe recovery, the controlled exception path and whether unaffected work may continue or the user must stop and escalate.
When should a user go to Support Central?
When the issue is account-specific, requires intervention or investigation, indicates a bug/incident, or documented safe recovery did not resolve the problem.
Should old articles remain searchable?
Superseded articles can retain historical value, but they should be clearly marked, linked to the replacement and not outrank the current maintained procedure.
Can an error message link directly to a troubleshooting article?
Yes. Contextual help is valuable when it points to the current canonical article and does not expose sensitive diagnostic information.
How should support feedback improve Help Center?
Repeated support cases, failed searches and product/process changes should trigger review of the relevant canonical article, search terms and exception guidance.
Make the maintained answer easier to find than the workaround
Find the Right Task, Follow the Current Procedure, Verify the Result and Escalate only when Investigation Is Required
Help Center should shorten the path from question to correct action while protecting inventory, custody and commercial state from unsafe shortcuts or stale guidance.