Your wholesale portal doesn't have a "single help center screen" where you load everything. The information you want to communicate to buyers (FAQs, commercial terms, instructions, legal data) is spread across several places in the platform depending on where you want it to appear. This guide explains where to put each thing.
Web FAQs (How to buy section)
The standard way to load FAQs visible to buyers in your storefront is the How to buy section. It's edited in Settings → Communication → How to buy with the rich editor (bold, lists, headings, links, images, etc.).
The default text already includes an FAQ structure ready to replace:
- How do I place my first wholesale order?
- What's the minimum order?
- How do I receive my order?
- How do I become a distributor?
- I want to buy for personal use, where can I get it?
What you load there appears as a dedicated page in the portal accessible from the navigation. It's the most visible place: if a buyer has a general question about your wholesale operation, that's where they'll find the answer.
Chat widget FAQs
Independently from How to buy, you can load short question/answer pairs that appear as quick buttons inside the chat widget in the storefront. Configure them in Settings → Chat → FAQs (:negocio/chat-preguntas).
Each entry has:
- Question — chat button text (short, one line).
- Answer — text shown when the buyer clicks the button.
Useful for resolving quick questions without taking the buyer out of the catalog (for example, "Do you ship nationwide?", "Do you accept credit cards?", "What are your business hours?"). If the answer needs more space or formatting, put the detail in How to buy and keep the chat for operational questions.
About us and custom section
To tell the business story, showcase brands you work with, supply capacity, certifications, etc., use:
- About us (
Settings → Communication → About us) — rich text. The page activates in the portal when you add content. - Custom section (
Settings → Communication → Custom section) — an additional page with a title and content of your choice, ideal for product dossiers, long-form instructions, use cases, etc.
Checkout notice
The Checkout notice before finalizing the order (Settings → Communication → Checkout notice) appears on the last step of the buyer's purchase flow. It's the right place for commercial terms worth reinforcing before close: assembly times, stock policy, possible total adjustments, shipping terms, etc.
Header announcement
The top announcement bar (Settings → Communication → Header announcement) is the first line visible when entering the portal. Works for short operational messages: "Shipping until December 22", "Minimum order from $X", "New price list effective Monday". Accepts links and images.
Information in automatic emails
Every automatic email sent to the buyer (welcome, pending registration, order received, order cancelled, order edited) has its own editable body in Settings → Communication → Automatic customer emails — see Automatic customer emails.
Use them to reinforce recurring messages: in the welcome email walk through the steps, in the order-received email detail the assembly times and payment methods, and so on.
Campaigns and automated email replies (Auto-seller)
To respond with information based on buyer behavior (abandoned cart, inactivity, didn't complete first purchase), use Marketing → Auto-seller — see Auto-seller. Each trigger lets you write subject + body and optionally attach a coupon. It helps resolve "didn't understand how to proceed" before the case goes cold.
Banners and home page
The promotional banners and home page blocks (Settings → Communication → Home page) are also places where you can drop informational messages: an image with text and a link to How to buy, or a featured block titled "How to buy" with a short paragraph.
Contact form
The storefront's contact form is customized in Settings → Contact:
- Banner (
:negocio/contacto-banner), Title and Subtitle of the contact page. - Custom questions (
:negocio/preguntas-contacto) — extra fields the buyer fills in besides name/email/message. Use them to categorize inquiries (business type, products of interest, expected volume). - The business contact details (address, phone, mobile, emails) are shown at the bottom of the form, loaded from General settings.
The buyer reaches the form via the "Contact" portal link or from the Contact tab inside the chat widget.
Legal pages (privacy, terms, returns)
Policies and terms are also controlled from Settings → Communication → Other:
- Privacy policy (
:politicas-privacidad) — markdown text shown at the portal's/politicas-privacidadURL. - Terms of use (
:terminos-de-uso) — markdown text at/terminos-de-uso. - Returns / cancellation policy — besides the text, the
/arrepentimientopage shows a form so the buyer can submit a cancellation request.
What does NOT exist (important clarifications)
- ❌ There is no built-in "tutorials with videos" section in the wholesale portal. If you want to walk buyers through a step-by-step process (how to register, how to place an order), write it in How to buy, in the Custom section, or as a Home page block. You can embed images and videos via markdown/HTML in any of those editors.
- ❌ There is no internal search across the portal's FAQs. The How to buy section is continuous text; structure it with headings (H1/H2/H3) and lists so it's easy to scan.
- ❌ There is no dedicated "report a bug" form for buyers. If a buyer hits a technical issue, the standard channel is the Contact form or the chat widget.
Tips
- Think of information in layers: the chat widget resolves operational questions in seconds, How to buy explains the full process, the checkout notice reinforces critical terms, automatic emails accompany each step of the order. Keep them consistent.
- Structure How to buy with clear headings (H2 per FAQ) to make up for the missing search — buyers scan rather than read.
- When operational terms change (minimum order, shipping times, price list), update the relevant places at once: How to buy, checkout notice, chat FAQ and the matching automatic emails.
- For technical questions about the platform itself (how to create a product, how to approve a buyer, etc.), your team also has the AI Assistant built in — see AI Assistant.