How to Create a Customer Service Knowledge Base for Your Ecommerce Store

If roughly a third of your support tickets are people asking where their order is, your knowledge base does not need to be complicated. One well-written article that answers that question, linked from your order confirmation email and your product pages, deflects a measurable share of that volume before it reaches your inbox. This guide covers how to build an ecommerce knowledge base from scratch: what to put in it, how to structure it, and how to measure whether it is working.

At a Glance

• WISMO queries can make up 30-40% of ecommerce support volume.
• A knowledge base deflects tickets before they ever reach your team.
• Five article types cover the most common ecommerce query categories.
• eDesk’s knowledge base tool publishes articles and tracks deflection rate.
• Start with 5 articles and expand based on what buyers still ask.
• Measure success by ticket volume reduction, not article page views alone.

Why Ecommerce Knowledge Bases Are Different

A SaaS company’s knowledge base is full of feature walkthroughs, API docs, and billing FAQs. An ecommerce seller’s knowledge base is almost entirely post-purchase: buyers want to know where their order is, how to return something, what your policy covers, and whether you ship to their country. These questions are predictable, repeatable, and answerable without a human. That makes them ideal for self-service deflection.

The ecommerce-specific knowledge base is not a documentation library. It is a ticket deflection tool. Every article that answers a question the buyer would otherwise have emailed about is a ticket that does not reach your support queue. Marketplace sellers get additional benefit because a link to your returns policy article, placed in your Amazon or eBay seller profile, handles the pre-purchase questions that buyers on those platforms ask most often.

How to Build a Customer Service Knowledge Base in 5 Steps

1. Identify your top ticket types from the last 30 days. Before you write a single article, pull a breakdown of your ticket types from your helpdesk. Group tickets by question type: order status, returns, delivery, product queries, payment, and other. The top three or four categories are your first articles. If you do not have helpdesk data yet, common sense covers most of it: WISMO, returns, and your return policy are the starting point for almost every ecommerce store. The goal is to write articles for the questions you answer most often, not the questions you think buyers should be asking.
2. Define your knowledge base structure. Organise your articles into sections that match how buyers think, not how your internal teams are organised. A useful structure for most ecommerce stores is: (1) Orders, covering status, tracking, and delivery. (2) Returns and refunds. (3) Products, covering compatibility, sizing, and specifications. (4) Shipping, covering timelines, international, and carrier options. (5) Payments, covering methods, charges, and billing. Start with these five sections and one article per section. Buyers should be able to find the answer to any common question in two clicks from the knowledge base home page.
3. Write one article per high-frequency query type. Each article should answer a single question, completely, in plain language. Avoid internal jargon, marketing language, and anything that requires the buyer to click to another page to get the full answer. Write the answer first, add context second. For WISMO articles, include the exact tracking link format and what to do if tracking is not updating. For returns articles, include the step-by-step return process and the refund timeline. A buyer who reads the article and still has a question should be rare. If articles are generating follow-up tickets, they need to be rewritten, not supplemented.

See how eDesk’s knowledge base tool tracks which articles deflect the most tickets. Explore eDesk Knowledge Base

1. Publish in eDesk and link from every relevant touchpoint. In eDesk, publish your knowledge base articles through the built-in knowledge base feature. Once published, link to relevant articles from: your order confirmation email (link to the tracking and WISMO article), your returns process email (link to the returns and refund article), your store’s FAQ page, your marketplace seller profile where permitted, and your auto-reply when a ticket is received. The article only deflects tickets if buyers can find it. The most commonly missed placement is the auto-reply on ticket receipt: a message that says “while you wait for our response, you might find your answer here” with a link to the relevant article deflects a meaningful share of tickets before an agent replies.
2. Measure deflection rate monthly and update articles that are not working. eDesk reporting shows how many buyers viewed a knowledge base article before or instead of submitting a ticket. This is your deflection rate. Review it monthly. Articles with high view counts but still-high inbound ticket volumes on the same query type need to be rewritten: buyers are finding the article but not getting the answer from it. Articles with low view counts need better placement or better titles. The knowledge base is a live document. Update articles every time your return policy, shipping carrier, or delivery timeline changes.

The 5 Articles Every Ecommerce Knowledge Base Needs

Start with these five before adding anything else. Together they cover the majority of inbound volume for most online stores.

1. Where is my order?

What it answers: How to find tracking information, what the tracking statuses mean, and what to do if the package appears to be delayed or lost.

Writing tips: Include the actual tracking link, explain what each common carrier status means in plain English, and give a clear action the buyer can take if tracking has not updated in 48 hours. This article alone deflects more ticket volume than any other in a typical ecommerce knowledge base.

2. How do I return an item?

What it answers: The step-by-step return process, what is and is not eligible for return, and how to initiate a return.

Writing tips: List each step as a numbered action. Include the return window, how the buyer labels the parcel, where they send it, and what to do if they bought through a marketplace (Amazon and eBay both have their own return portals, which differ from a direct store return).

3. What is your return policy?

What it answers: The terms of your return and refund policy: timeframes, conditions, exceptions, and refund processing time.

Writing tips: Write this as a plain-language summary, not a legal document. Buyers read this when they have already decided to return and want to know their rights. Include the refund timeline from the moment the item is received back. For marketplace sellers, note that the marketplace’s buyer protection policy may differ from your own.

4. How do I cancel my order?

What it answers: Whether cancellation is possible, at what stage, and how to request it.

Writing tips: Be direct about the cancellation window. If an order can only be cancelled within 30 minutes of placement, say so clearly. If it cannot be cancelled once dispatched, explain the return process as the alternative. Buyers who ask about cancellation and cannot cancel often become returns in any case, so link to the returns article at the bottom.

5. Do you ship internationally?

What it answers: Which countries you ship to, delivery timelines, any import duties the buyer may face, and how to check if your store ships to their location.

Writing tips: This article reduces pre-purchase queries as well as post-purchase confusion. Include estimated delivery windows by region. If you sell on marketplaces with their own shipping programs, note that marketplace-fulfilled orders may have different coverage than your direct store.

What Deflection Actually Looks Like

WISMO articles in ecommerce knowledge bases deflect 20-40% of inbound order-status ticket volume in typical ecommerce accounts, based on eDesk platform data. [Editor: confirm this figure with the eDesk product or data team before publishing, and add the time period and sample size.]

The deflection rate for other article types is lower but still material: a well-placed returns policy article reduces the pre-return inquiry volume, which is the tickets that ask “can I return this?” before the buyer has initiated anything. Fewer pre-return inquiries means fewer tickets that require a human response to confirm what the policy already says.

What This Looks Like in Practice

A two-person team running Amazon and a Shopify store was receiving roughly 150 tickets a week, with an estimated 40% of them being order-status queries. They had no knowledge base and no FAQ page. After publishing a WISMO article in eDesk’s knowledge base tool and linking to it from their order confirmation email, order-status inbound tickets dropped measurably within two weeks. They added a returns article and a return policy article in week three. By the end of the first month, ticket volume had reduced enough that both agents were handling the queue without weekend overtime for the first time in four months.

Key Takeaways

• Build your first five articles around your actual top ticket types, not what you assume buyers want to know.
• Write each article to answer one question completely, with no need to follow up with support.
• Publish in eDesk’s knowledge base tool and link from every relevant buyer touchpoint, including your auto-reply email.
• Measure deflection rate in eDesk reporting monthly and rewrite articles that are not reducing inbound volume on the same topic.
• Start with five articles and expand based on what buyers are still asking after the knowledge base goes live.

FAQs

What should I put in a customer service knowledge base for ecommerce?

Start with the five highest-frequency query categories for most online stores: order status and tracking, returns process, return and refund policy, order cancellation, and international shipping. These five topics cover the majority of inbound support volume for most ecommerce operations. Write one article per topic, answer the question completely, and expand to additional topics based on what buyers are still contacting support about after the knowledge base goes live.

How does a knowledge base reduce support tickets?

A knowledge base reduces tickets by giving buyers a way to answer their own question before they contact support. When a buyer can find the tracking article from their confirmation email, they do not need to email asking where their order is. When they can find the returns process from a link in your seller profile, they do not need to message you to ask how to return something. Every article that answers a question the buyer would otherwise have contacted you about is a ticket that does not enter your queue.

What is the best knowledge base software for ecommerce?

For ecommerce sellers on Amazon, eBay, and Shopify, eDesk’s built-in knowledge base tool integrates directly with your support inbox and tracks deflection rate alongside your ticket data. This means you can see in the same dashboard how many tickets arrived on a given day and how many buyers found their answer in the knowledge base instead. Zendesk and Freshdesk both offer knowledge base features but do not have the same marketplace-native order context, which limits how precisely you can link articles to the ticket types they are designed to deflect.

Related: eDesk knowledge base tool | how to automate ecommerce customer support | how to handle customer complaints

Ready to publish your knowledge base and track ticket deflection in one place? Start you