Solutions · Sectors · Retail and wholesale
The customer is at the counter. The answer cannot depend on who is on shift.
Across a chain, the same question arrives a hundred times a day in twenty different places — answered by a team that keeps changing. How many months of warranty does this product carry? Does a return without the receipt count? Is last week's promotion still running? Skyller publishes the chain's rule once, answers with the document alongside, and drops from the answer whatever has expired. It does not open your sales system and it does not check stock levels.
- The same rule in every store
- Promotions within their validity
- Retail profiles
- Stock in your system
Who works here
From head office to customer service.
The chain's rules and supplier material reach the people selling, buying and deciding on exceptions.
Consistent answers
How it works today
Asks the colleague next to them, and the answer changes depending on who answers. When nobody knows, they call head office while the customer waits.
With Skyller
Asks in the chat and gets the answer with the chain's document alongside, effective date visible.
Focus on exceptions
How it works today
Repeats the same explanation to every new hire and becomes the phone number the team calls whenever an exception comes up.
With Skyller
Publishes the rule once and receives the exception as a card with an owner and a due date, instead of a loose message.
Information for the shop floor
How it works today
Keeps datasheets, supplier price lists and warranty policies in a folder only they know how to open.
With Skyller
Uploads the supplier material into the purchasing workspace and it starts answering — scanned PDFs included.
Current terms
How it works today
Works from the price list downloaded last week and finds out too late that the terms have changed.
With Skyller
Checks the current terms from their phone; the expired list has already left the answers.
The routine of the people who sell
From the supplier datasheet to the till, with the limit written down.
See what Skyller does, what needs configuration and what stays with your team.
Select a routine to see the details.
Skyller does it
The returns and warranty rule
The Warranty and Returns Policy and the Returns and Exchanges Process start from ready-made templates in the platform library, go through second-person review and are published. Only the published version answers, and the previous one is kept.
«How many months of warranty does it have?»
Whoever is serving asks in the chat and gets the answer with the document alongside, so they can check the source before speaking to the customer. The answer comes from what the chain published, not from a generic opinion.
Material arriving from the supplier
Datasheets, manuals, price lists and warranty terms come in as PDF, Word, PowerPoint, Excel, CSV, HTML, text, scanned image or audio. Anything scanned goes through image reading before becoming searchable text.
Campaigns and price lists with an end date
Every document carries an effective date and an expiry date. Once the expiry passes, it stops answering and leaves the assistant's inventory — nobody offers the finished promotion without noticing.
The exception that needs authorisation
A case outside the policy becomes a card with store, customer, reason and owner, and the reminder goes out 24 hours before the due date and on the day itself, once each, to whoever is on the card. The person who authorises is still the manager.
New people on the shop floor
From the published text itself comes an assessment of 3 to 20 questions, assigned to people and teams with a deadline. You see who took it and what they got right; certificates and course tracks do not exist in the product.
Purchasing and suppliers
The Purchasing and Procurement Policy, the Supplier Quotation and Selection Process and the Supplier Code of Conduct start from ready-made templates and begin answering what to attach and who authorises. The negotiation stays yours.
Depends on configuration
Stock counts and out-of-stocks
Stock Management and the Physical Inventory Process become published procedures, and the count can become a board with stages, owners and due dates. The physical check and the correction in your system stay with the team.
The store system and the online shop
The catalogue carries ready-made commerce and spreadsheet connections. Your chain's point of sale or ERP may not be among them — and that does not close the door: any system that exposes a bridge comes in through its address, with a secure connection required and function-by-function clearance, built by the system's vendor, by your IT or by a partner — or by Skyller as a separate service.
Stays with the team
Selling, charging and writing off
The price actually charged, stock balances, invoicing, authorising the exchange and the money in the till stay in your system, with your team. Skyller does not check balances, does not change prices and does not issue tax documents.
Some routines require connecting a system or adjusting your company settings.
Live proof
Saturday, 11:40. A return outside the window and a queue behind it.
A chain is not tested on the day the policy is written: it is tested on the Saturday when the store is full, the person serving started three weeks ago and the customer has a reasonable argument.
Starting point
A customer wants to exchange a product bought 45 days ago, without the packaging. The assistant joined three weeks ago. The policy exists, in a PDF that circulated by email in May and that nobody is sure was ever updated.
What happens
- Operations opens the library, picks the Warranty and Returns Policy and adjusts the chain's windows. The draft already arrives with the company name, the owner and the date filled in. It goes for review: whoever wrote it does not review their own text, and being an administrator does not give anyone, on its own, the right to approve. The regional manager reviews it from her phone and publishes.
- At the counter, the assistant asks from her phone whether an exchange without packaging, after 30 days, has an exception. The answer arrives with the policy alongside; a tap opens the published document, with type, owner and effective date visible. The May version no longer answers.
- The case is an exception. The assistant asks Skyller to open a card on the authorisations board with store, customer, reason and today's due date; the card is created with an owner. The regional manager gets the reminder and decides.
Result
The customer hears the same answer she would hear in any store in the chain, and the exception becomes a request with an owner and a due date instead of a message that gets lost. The decision still belongs to the manager; the exchange, once authorised, is recorded in the store system by the team.
What this scene does not promise
- Skyller does not look up the invoice, the stock balance or the price actually charged. It answers from what the chain published, not from your sales system.
- It does not authorise the exchange, does not refund, does not issue invoices and does not touch the till. None of that exists in the product.
- Your chain's point of sale or ERP may have no ready-made connector in the catalogue. Beyond it, the route is the system's own bridge address — built by the vendor, by your IT or by a partner, or by Skyller separately.
- Opening the card is an action taken by the person who asked, with their own permissions — it is not an approval. The confirmation Skyller asks for before acting appears in other actions, such as creating a board or archiving one.
Scene with a fictional chain, customer and deadline; the library, second-person review, document expiry, the answer with its source alongside and the card with an owner and a due date are the product's own.
What holds the routine together
Nine pieces the chain uses every day, from the counter to head office.
Select a feature to see how it works.
One published rule, and it is the one that answers
The chain decides which document types require review and approval. Where they do, whoever wrote the text does not review it, and the authority to approve comes from a responsibility assigned to people — not from an administrator badge. Drafts and documents under review do not enter the answers; the previous version is kept.
An expiry date that pulls the campaign out of the answer
Price lists, campaigns, commercial terms and warranty statements carry effective and expiry dates. Once the expiry passes, the document stops answering and leaves the assistant's inventory — the same criterion in both places, so the assistant never cites what retrieval will refuse. Periodic review is a different thing: it flags, it does not remove.
Templates in Portuguese for the chain's rule
The Warranty and Returns Policy, the Returns and Exchanges Process, Stock Management, the Physical Inventory Process, the Sales Manual, Customer Service Excellence, the Purchasing and Procurement Policy and the Supplier Code of Conduct are already in the library. Skyller fills in company, owner and date; anything missing stays in the text as a field for you to complete.
Supplier material, in any format
PDF, Word, PowerPoint, Excel, CSV, HTML, text, scanned image and audio. A scanned datasheet goes through image reading before becoming searchable text, and the file enters the workspace with a type, an owner and a date.
Sector profiles ready to install
Store Manager, Inventory and Stock Analyst, Pricing Analyst and Purchasing Analyst sit in the platform library. On the agents screen you filter by Segment and see the profiles for your sector. A platform profile cannot be edited: you use it as it is, or duplicate it to create your own version.
The exception with an owner, a stage and a due date
You build the board with the chain's own fields — store, customer, reason, amount, owner — from fifteen field types, and a field made mandatory at a stage stops the card from advancing without the evidence. The reminder goes out 24 hours before the due date and on the day itself, once in each case, to whoever is on the card.
The question that sweeps the board
«What is overdue?», «what is with the Centro store?», «what is stuck at the review stage?» — Skyller reads the board by stage, by owner and by overdue date and returns the list, respecting the visibility configured. It counts cards; it does not add up amounts or build indicators.
Training whoever started this week
From the published text comes an assessment of 3 to 20 questions, with 2 to 6 options and a pass mark set by the chain, assigned to people and teams with a deadline. Each person gets the reminder with the deadline. There are no certificates, course tracks or automatic chasing of whoever has not taken it.
Where Skyller stops
It has no stock, pricing or invoicing module: it does not check balances on its own, does not issue invoices and does not process refunds. What it reads from a retail system is what that system exposes and your chain has released — through a ready-made connector from the catalogue or through the system's own bridge address, function by function.
How this enters the chain
Start with one question, not with the whole chain.
The first week needs no project. Pick the question that most often makes a store call head office, publish its answer and let the counter test it.
Operations
Creates the chain's hub and defines who joins: one workspace for the rule that applies in every store and another for purchasing and suppliers.
Owner, editor and reader roles per person or per team. A private workspace answers only to the people inside it; a public hub is read by the whole company.
Operations
Opens the library, picks the Warranty and Returns Policy and adjusts windows, exceptions and who authorises each one.
The templates are Skyller's and work on any plan; the document created counts towards the subscription's document allowance.
Regional management
Reviews and publishes. From then on, that policy is what answers when somebody asks at the counter.
Whoever wrote the text does not review it when the document type requires review. Only the published version enters the answers.
Store
Asks in the chat while serving and checks the answer against the document opened alongside.
Anyone above viewer level installs the sector profiles from the library and uses them day to day.
Operations
Builds the exceptions board with the chain's fields and turns on due dates, so the request stops living in a conversation.
A field made mandatory at a stage stops the card from advancing without the evidence; the due-date reminder goes to whoever is on the card.
Comes ready
- Policy and process templates in Portuguese, covering warranty, returns, exchanges, stock, inventory, purchasing and customer service
- Sector profiles to install: Store Manager, Inventory and Stock Analyst, Pricing Analyst and Purchasing Analyst
- Effective and expiry dates on every document, with automatic removal from the answers once the expiry passes
- Boards with fifteen field types, mandatory fields per stage and reminders 24 hours before the due date and on the day
- Assessments generated from the published document itself, assigned to people and teams with a deadline
Your company decides
- Which workspaces exist, who joins each one and with which role
- Which document types require review and approval before publishing
- Which boards exist, with which stages, fields and due dates
- Whether the online shop, the spreadsheet or the internal system come in as connections, and which functions stay cleared
Questions from the people running the store
The doubts that come up before the first store goes into Skyller.
Start with one question
Publish the returns rule. Let the counter ask.
Create the account, open the chain's workspace, publish the policy that most often makes a store call head office and ask three assistants to try it from their phones during a shift. In a week you know whether the answer arrives the same in every store — which is the only proof that matters here.