Website and online store

Website and store in the same system as orders.

Pages, blog, forms, chat, and product catalog in Kinsu ERP itself, with the system’s prices and inventory. Vítor Assis, an AI agent, keeps pages and products up to date, and Henrique Quintela writes the blog. Anything that goes live passes through a person.

Online store manager checks the day’s orders on a phone, next to the packing table with boxes and a laptop
Example · Online order 0457Filial Curitiba
CustomerPapelaria Central
Items12 boxes of A4 paper · 4 toner cartridges
ValueR$ 2.318,40
StatusAwaiting picking
Inventory · reservesTeam · delivers
Illustrative values.
Vítor Assis

Vítor Assis

Website and online store · Pages, products, and contacts

AI agent

The module’s agents

You publish. Vítor prepares pages, products, and contacts.

Vítor Assis updates pages, menus, images, and products from a request in the chat. Changes stay in draft until someone on the team reviews and publishes them. Each form received becomes a contact and goes to the right person. Henrique writes the blog, and Valentina translates.

Vítor Assis
Vítor Assis
AI agentWebsite and online store
Henrique Quintela
Henrique Quintela
AI agentBlog
Valentina Ortiz
Valentina Ortiz
AI agentTranslation
Example · conversation with VítorWebsite · Matriz São Paulo

Did any quote requests come in through the website today?

Vítor Assis
Vítor AssisAI agentWebsite and online store

3 came in. The one from Laticínios Boa Vista, for 400 rolls, became a lead with source “website form” and went to Gustavo for scoring. The other 2 are from Filial Campinas customers and are in the queue of the sales rep there. Replying to each one is up to the sales rep.

Awaiting the sales rep
Illustrative example.

Updates pages, menus, and images from a request in the chat

Keeps store products in line with the price list and stock availability

Records each form received and routes it to the owner

Shows on the website only the videos a person marked public; private ones stay out

Prepares and updates marketplace listings from the product records, in the 8 languages

A new website or a campaign landing page? Lívia Monteiro, an AI agent, creates each one from a request in the chat and leaves it as a draft and preview until a person approves and publishes it. After launch, day-to-day work continues with Vítor.

Lívia Monteiro
Lívia Monteiro
AI agentWebsite creation
See website creation

Company website

Pages, blog, and languages, edited in the system itself.

The website is built in Kinsu ERP, with pages, sections, menus, theme, images, and blog. Each country or language has its own address, such as /br or /us, and its own legal page. The team edits, Vítor prepares the changes, and nothing goes live until a person publishes it.

Example · company websiteCustom domain
Pageshome, products, services, blog, and contact
LanguagesPortuguese and Spanish
Themecompany logo, colors, and photos
New blog postprepared by Henrique · edited by the team
StatusDraft · awaiting publication
Illustrative example.

Custom domain with automatic HTTPS and a theme with the company’s logo, colors, and photos

Company, product, and service pages, and a blog

Multiple languages and countries, each at its own address

Title and description for each page, a sitemap for search engines, and redirects

Draft and preview before publishing

Translation

You review and publish. Valentina translates into the 8 languages.

Valentina Ortiz, an AI agent, translates the website pages, records, and product catalogs into the 8 languages, with your company glossary. A person reviews and publishes what goes public.

Valentina Ortiz
Valentina Ortiz
AI agentTranslation
Example · conversation with ValentinaWebsite · Matriz São Paulo

Valentina, translate the packaging line pages and the new catalog products into Spanish.

Valentina Ortiz
Valentina OrtizAI agentTranslation

I translated the 3 pages and the 12 new products into Spanish, using the terms from the company glossary. The translations stay in draft until someone on the team reviews and publishes them.

Awaiting review
Illustrative example.

Translates the website pages

Translates product records and catalogs

Uses the company glossary in each language

Works in Portuguese, English, Spanish, French, German, Italian, Japanese, and Chinese

Blog

Henrique writes the blog. A person publishes it.

Henrique Quintela, the AI agent for the blog, handles the topics, research, writing, and SEO, in 8 languages. Each post stays as a draft, with a preview, until someone on the team publishes it.

Henrique Quintela
Henrique Quintela
AI agentBlog

Topics and research

Henrique proposes the topic and researches the subject.

Henrique QuintelaHenrique · researches

Writing and SEO

He writes the post, with the title and description for search engines.

Henrique QuintelaHenrique · writes

Eight languages

The post gets versions in the 8 languages.

Henrique QuintelaHenrique · prepares

Draft, preview, and publishing

Everything stays in draft, with a preview. A person on the team publishes.

Team · publishes

Website forms and chat

Whoever writes in through the website becomes a contact, with source and owner.

Forms and chat are linked to the sales pipeline and customer service. Each submission is recorded in the system, with its status and the person who will reply.

Forms that become contacts

Quote, visit, or contact requests: each submission is recorded as new, read, replied, archived, or spam, and becomes a lead with its source marked.

Rule-based routing

Vítor routes the contact by the company’s rule: by branch, by product, or by region. The lead enters the pipeline for Gustavo to score.

Website chat

Larissa handles the website chat, including anonymous visitors, with the answers the company defined and with conversation limits and retention. The conversation is saved to the lead or customer record.

Videos with their own page

Videos marked public in the sales catalog get a page on the website, with the transcript. Private ones stay out.

Website features

Protected forms, videos, members, and subscriptions.

Features to protect forms, know where each contact comes from, show videos, and sell subscriptions, on the website your company builds in Kinsu ERP.

reCAPTCHA on forms

The website forms use reCAPTCHA.

Source through to checkout

UTM attribution carries through to the form and checkout.

Hosted videos

Adaptive streaming, resume where you left off, statistics, and captions.

Members and previews

Members-only pages and signed preview links.

Markets and legal text

Sections by market and legal text by jurisdiction, such as LGPD and GDPR.

Subscriptions

Subscription checkout with a billing portal (Stripe).

Online store

From online order to invoice, each step with its owner.

The store uses the Kinsu ERP product catalog, price lists, and inventory, with no second product database to maintain. Example: Online Order 0457, from Papelaria Central.

The customer places the order

In the store catalog, products appear with the price-list price and the branch’s availability. The order comes in as a sales order, linked to the customer record.

Customer · requests

Inventory reserves

The items are reserved at the Filial Curitiba warehouse, and availability in the store follows the stock balance.

Inventory · reserves

A person issues the invoice

Tatiana prepares the NF⁠-⁠e with the registered tax rules, and a person on the team issues it. The charge goes into accounts receivable.

Team · issues

Picking and delivery

The team picks, packs, and ships. Larissa updates the customer at each stage of the order.

Team · delivers

Marketplaces

Your store and the marketplaces, on the same inventory.

Marketplace orders arrive in Kinsu ERP as sales orders, with your product records, price lists and inventory. Each marketplace is connected by API and configured with the Kinsu team, like the other integrations.

Vítor Assis
Vítor Assis
AI agentWebsite and online store
Example · Marketplace orderFilial Curitiba
ChannelAmazon
OrderSales order 0458 · 3 items
InventoryReserved at Filial Curitiba
ListingStock updated in the store and on the marketplace
InvoiceWaiting for the team
Illustrative example.

Vítor prepares and updates the listings from your product records, in the 8 languages

A person on your team publishes the listings

The marketplace order comes in as a sales order, linked to the customer record

The inventory balance updates the store and the marketplaces

A person on your team issues the invoice and ships

API integration with these and other marketplaces

Shopee
Magalu
eBayWalmartTmall

What stays with people

The agents prepare. People publish, reply, and sell.

Vítor, Henrique, and Valentina work with the actions enabled for them. What goes live and what is agreed with the customer stays with the team.

Publish on the website

Changes to pages and products, marketplace listings, blog posts, and translations stay as drafts until a person reviews and publishes them.

Reply to each contact

Vítor records and routes the forms. The sales reply belongs to the sales rep, and the lead follows the pipeline rules.

Price and invoice

Store prices come from the price lists the company approved. Each order’s invoice is issued by a person; issuing is an action the agent does not perform.

Agent permissions

The administrator chooses what Vítor, Henrique, and Valentina can change on the website and can turn off the agents in the account. The website stays with the team.

Questions about the website and online store.

No. The website, blog, forms, and store are built in Kinsu ERP itself. The team edits the pages, and Vítor prepares changes for review.
Yes. The website uses your company’s domain, with its theme, logo, colors, and photos.
Yes. Each language or country has its own address, such as /br and /us, with the translated pages and that country’s legal page. Valentina translates using the company glossary, and a person reviews before publishing.
It is logged as new, becomes a lead with source “website form”, and goes to the responsible person, following the rule the company defined. The status changes to read, replied, or archived as the team works.
Yes. Store products come from the Kinsu ERP product records, with each branch’s price lists and availability. The online order comes in as a sales order, like the others.
Yes, with the API integration configured with the Kinsu team. Orders come in as sales orders, with your inventory and price lists. Vítor prepares the listings from your product records, and a person on your team publishes them.
A person on the team. Tatiana Brandão prepares the invoice with the registered tax rules and sets aside what the accountant needs to validate. Issuing is always a person’s action.
A person on the team. Henrique Quintela, an AI agent, handles the topics, research, writing, and SEO in 8 languages, and each post stays as a draft, with a preview, until it is published.
Data import, such as the product catalog, is done with our team and assessed case by case. The pages of your current site serve as the basis for the new ones.
Yes, with subscription checkout and a billing portal (Stripe).

See the website and store at work, from form to order.

In the demo, we show a sample website with a blog in two languages, a form that becomes a lead, and an online order that reaches inventory and tax.

Join the waitlist