Release history

In the purchase invoice entry, the Payment block has "Who gets paid". Pick the partner who paid with their card and set the installments, the 1st due date, the financial category and the profit center: the payable is created in installments in the partner's name, with the purchase month as the accrual period. Leave it empty and payment still goes to the invoice issuer, as always.

The item list of the purchase invoice entry has a new Destination column. Inventory goes into the stock balance, as always. Use and consumption does not go into stock and needs no registered product. Fixed asset becomes the asset record when you post, linked to the payable. The warehouse is only asked for when some item goes to inventory.

The supplier record has a new "Partner who gets reimbursed" option. Check it on the record of the partner who pays company purchases with their card or account: only they appear in "Who gets paid" on the purchase invoice entry, and only they allow keeping an invoice under a third party tax ID as a receipt. Ask Tenkai "how much does the company owe me in reimbursements?".

In the work order, choose the Mode. Service is a consultant's work: pick the project and the phase and log the hours — no GPS, materials or on-screen sign-off. Field is the usual work order, with everything it already had. Your existing work orders stay as field, unchanged.

In the work order Hours tab, approve the hours: once approved they draw down the contract hour bank and enter profitability the same day. If the work order came from a request, the work order hours win — hours logged on the request itself stop counting, so the same hour never counts twice. Waived and non-billable hours do not draw down the bank. Rejected? The hour leaves everything.

In Employee cost, each validity period now has "Entered hourly cost". Fill it in for contractor consultants or anyone with a negotiated hourly cost: that value is used in every margin instead of monthly cost ÷ working hours. Leave it empty and nothing changes. Only people who can see amounts can see and edit it.

In the project record, the "Project P&L" tab shows month by month the revenue sold (hours × price of each role, plus the project manager %), the cost of the hours worked by whoever worked them, overhead at the % you set and the margin — planned and actual side by side. Click a cost to see it by phase, consultant and work order. Hours without a person, phase or hourly cost show up in an open-issues line. Export to Excel, CSV or PDF.

In the "Phases, milestones and requests" tab, "Apply standard phases" creates the phases of your model (scope assessment, configuration, user acceptance, training and simulation, go-live, hypercare) without touching the milestones you already have; each phase keeps its hours sold. In the P&L, choose how revenue becomes a month — equal installments over N months, by % of completion or on delivery of each phase — and "Generate revenue schedule" writes it to the same schedule the accountant recognizes. The new "Timeline" tab brings phases, client decisions, requests, work orders and invoices together by date.

In the Work orders list, Import spreadsheet accepts the Sankhya work order report: each row becomes a service work order with its hours already approved (you are recorded as the approver), linked to the consultant, project and phase. Importing the same file again duplicates nothing.

In the Sankhya connector (it can be registered without a password: import is by file), the mapping shows how Sankhya names each consultant, project and phase and who they are in Tenka. Automatic suggestion matches by code, e-mail and name; what stays unlinked comes in as a pending item and links by itself once you choose.

In the project record, the Customer portal tab turns on what they see: the work orders carried out and the hours of each phase, sold and used, and, if you wish, who did the work. It starts closed: nothing shows until you turn it on, for the project or as the company default. Internal amounts never appear in the portal.

A posted entry now has a Reverse button, with the reason: stock gets the return movement, open installments (including the partner reimbursement) are cancelled and the fixed asset is written off, all recorded. If any installment was already paid, the reversal is refused and says which one — undo the payment first.

With acceptance turned on (on the project, the contract or as the company default), the work-order hours and the hours logged on a request that you approve wait for the customer's acceptance and only draw down the hour bank once they accept in the portal. Accepting, a comment is optional; rejecting, it is required — and the hour goes back to your approval. It comes turned off.

On the contract, the new Time entries tab lists the hours worked in two groups — those from work orders and those logged straight on requests — with date, consultant, whether approved and whether it already drew down the hour bank. No more empty requests tab when the hours come from work orders.

If your company uses work orders, Home gains four counters: work orders this week, hours to approve, projects with an overrun phase and contracts with overage to bill. Each leads to the right screen and only shows for people with access to it. If you don't use work orders, nothing new appears.

The Customers list gained the Exclusive companies column, which says which companies can see each customer (“All companies” when unrestricted), and a filter of the same name: “All companies” brings customers without restriction; choosing a company brings those restricted to it. In the dark theme, the Filters title is now legible.

The SOC 2 panel has a new Legal approval waiver section: the expense contracts where Legal approval was waived or required again in the last 12 months, with who did it and when. A waiver without an author or over a rejected approval shows as a control failure.

Write a line starting with "Solution:" in the commit message or the MR description, together with the #request code. The text goes into the request's Solution field, which the client sees in the hours report. It is added to what was already written, never erases it, and the rest of the message stays in the internal comment only.

When support replies, the client sees in red, in the portal, how many new messages arrived: on the Chat menu and on the chat button. The number goes away when they open the conversation.

When the client writes in the portal chat, the person responsible for the conversation gets a notice on the bell, with a link to Support. With no one responsible, everyone in support is notified. Several messages in a row become a single notice every 10 minutes.

On the contract Finance tab, each bill has Visible in portal. With no choice made, income shows and expenses do not, so the partner commission leaves the portal on its own. The contract value in the portal is income minus expenses of the visible bills.

On the contract record and in the portal contract, the chart starts at the total hours of the term and falls month by month by the contracted hours. The consumed line shows the actual up to today, and the trend carries the current pace to the end, telling how the contract will finish.

On the contract record, the Profitability tab shows where the margin comes from up to today: month by month (billed, labor, other costs and cumulative margin), by person (hours, average hourly cost and cost) and every other cost, line by line. Contract expenses in finance, such as the partner commission, now count in the margin and appear line by line. The Overview now shows the total contracted hours for the term, and bills in the trash no longer count as billed.

On the contract pack, choose the Hours cycle: Monthly, Quarterly, Half-yearly or Yearly. Hours renew every cycle, counted from the pack start, and the overage, the portal hour bank and the chart follow that cycle. With no cycle, the hours are valid for the whole term. The pack list shows each pack's hour bank and cycle.

On the contract page of the portal, the Contract summary button downloads a PDF with the whole contract: term, contracted items, contracted and used hours with the balance, month-by-month use, what was billed and paid, and the services with the team. The summary shows only what you already see on the portal.

In the export process, one click creates the export NF-e with the right CFOP, the importer abroad, the port of shipment and the DU-E when registered — in reais, at the process exchange rate.

When the team marks that the project is waiting for the client, the portal shows "Waiting for you", since when and why. The client clicks "I have answered — go ahead": the project moves again, the deadline counts again and the project manager is notified.

For stall accounts, Today now shows the business at a glance: sales today and this month, what was left (sales minus item cost), who owes and for how long, the month’s cash, how you get paid, stock, best sellers, orders and production — plus 6-month in/out charts, the best weekday and the month day by day. Each number opens the list behind it.

Scheduled questions now has "Import spreadsheet" (question, name, channel, destination, frequency, day and time). Every imported row starts turned off — nothing is sent until you review and turn it on.

In the account list, an account can be exempt from billing for a grace period, courtesy or demonstration, with the date the exemption ends. While it lasts, the account gets no invoice or payment slip, and access does not change. The day after the date, billing starts on its own; you get a notice seven days before and another on the day. BMCode's own account and the demonstrations are already exempt without marking anything.

The contract record has a new Requests tab: each request linked to the contract, with the logged hours, the ones that enter Profitability and the ones consumed from the contract, which are what the customer sees in the portal. When a request does not match in all three, the row says why: entry without a collaborator or date, request that does not consume the contract, consumption different from the hours. This is where you check, service by service, what the customer will check.

What used to be the status Category is now the Status classification screen. The five you already knew (Triage, In progress, Waiting, Done and Cancelled) come ready — you change name, color and order — and now you can create your own: each new classification becomes a section of the request Kanban. The status picks its classification from a list that comes from this screen, and the import spreadsheet accepts the key or the name.

In the contract Overview, the Contract hours block shows agreed, logged and consumed hours and the balance. Below, the term timeline compares the time elapsed with the balance used, and the burndown shows planned, actual and the trend to the end: how much balance the period ends with, or the day it runs out.

In the GitLab or GitHub connector, under Receive from git, choose the status a request goes to at each step: commit with #request code, MR merged into the integration branch, green pipeline on staging and release to production. The screen shows the webhook URL and generates its own secret, without exposing the access token.

Each sales order line now shows whether the piece is in stock, in production (with the current step and the expected date) or has no production planned (with the standard lead time). When the step is at a subcontractor, the date already adds that subcontractor's usual average delay. The catalog you send to stores shows the same sentence for the quantity the store typed, never any cost. The sentence says where the date comes from: "based on the actual production pace" when the step already has reports or scans and the subcontractor's measured punctuality, or "estimated" when it comes only from the standard step times or the product's standard lead time.

In Apparel production, PCP tab, register a 6-digit PIN for each production person or subcontractor and print the bundle labels with the scan QR code. Whoever has no account scans the QR code with the phone, types the PIN, chooses the step and the pieces — and the report goes in as usual, moving the actual cost of the piece and the promised date. Several wrong PINs block for 15 minutes, and the same report repeated within a few minutes is refused.

When the actual cost of a piece's last completed order goes over the spec sheet standard cost beyond the limit you set (5% by default), the wholesale price table gets the proposal of the new price that keeps your target margin, with the source of the number. Nothing changes on its own: whoever can edit the table applies it in one tap or discards it.

Through the portal link, the subcontractor now accepts or declines each shipment — declining comes with the reason — and Outsourced processing shows the acceptance of each batch, declined ones first. Each subcontractor gets an internal badge (gold, silver or bronze) calculated only from your own data: punctuality, defects on return, documents up to date and capacity. The badge shows in the punctuality table and when choosing the subcontractor for a shipment.

Send on WhatsApp a photo of the sales notebook page, of the Pix receipt your customer sent, of the purchase invoice (or its XML), or of a new item with the price in the caption ("ribbed blouse 29.90 S to XL"). Tenkai understands what it is and proposes: the notebook sales in the till, settling the customer's bill, the invoice into stock with the bill to pay, or the new item with the store's size grid and the photo. Nothing is saved before you reply CONFIRM. Notebook sales go into your till: open the till before sending the page. On a Pix receipt, write "recebi" (received) or "me pagou" (paid me) in the caption when money came in; "paguei" (I paid) never settles what a customer owes.

With the WhatsApp receipt switched on (Parameters, "Till: purchase receipt on WhatsApp"), when you close a sale at the till for a customer who has WhatsApp, she receives the items, quantity, amount and the photo of each style, in her language. Anyone who replied STOP does not receive it, and if your profile cannot see amounts the message goes out without them.

With "Daily summary: which summary to send" set to BALCAO and the summary switched on in My preferences, you get at 7 a.m., on WhatsApp or e-mail: how much you sold yesterday, how much you received, new credit sales, what sold out and tomorrow's group trip. If you asked for audio answers, it also arrives as audio.

Send "sold 30 of the ribbed top to Dona Maria, 20 by pix and 10 on credit" (typed or by voice) and Tenka shows the sale with the register price, the customer and the payment methods; it only enters today's register after you reply CONFIRM with the code. "Received 200 from Maria" (settles what she owes, oldest first) and "spent 200 on freight" (records the company expense) work too.

Ask "how much did I sell today?", "how much did I sell this week?" or "who owes me?" and the answer arrives at once, with the exact figure from the register and receivables and where it came from. "Collect from Maria" returns the link that opens the chat with her with the collection message already written: you check it and send it from your WhatsApp.

When a customer asks on WhatsApp "do you have 1234 in M black?", "what is the minimum?", "installments?" or "I want 12 of 1234 G blue", the reply comes from the stock and the terms the store registered, and the order is created as a quote for the salesperson to confirm. Whatever is not understood, or when she asks to talk to someone, goes to Conversations. Instagram Direct messages arrive in the same Conversations list.

Each store card shows customer conversations on WhatsApp over the last 30 days: how many were resolved without anyone from the store having to write, how much each conversation cost and how many minutes the customer waited for the first reply. One tap opens the store conversations.

Whoever prefers listening sends "reply in audio" on WhatsApp and starts receiving each reply also by voice, in their language. To go back to text only, send "reply in text". The preference belongs to each person.

Whoever does not have their own number yet talks to Tenka through BMCode's number: each message goes to the account of whoever wrote it, and one store's numbers never see another's. Whoever writes without an account receives, once a day, the link to create the account with just a mobile phone. The messages count toward your account's allowance.

Fair stalls and small apparel makers start for free: up to 30 registered items and 50 sales a month, with the phone checkout, Pix on your key and the list of who owes you. Beyond that, Tenka tells you right away and shows the Counter plan, R$ 59 a month, with no limit on items or sales. The Ateliê plan now costs R$ 149.

On the Start page the account is created with your WhatsApp number, a 6-digit code and your business name — no e-mail, no card. The number is already linked to Tenkai on WhatsApp, and you sign in later with the same code or a password, if you want one. Company ID and e-mail can be added later in Settings.

A phone screen with each customer, what is overdue and what is coming due, and a Collect button that opens the chat in your WhatsApp with the message ready. On a credit sale the customer gets the entry on the shop WhatsApp; two days before the due date and the day after, a reminder. On the Counter plan, customers without a set limit can buy on credit: the sale goes through and you are told.

If your company is a MEI, "How much I sold" and Home show how much of the yearly revenue limit you have used and alert you at 80% and 100%, citing the current rule. In the five days before the due date, a reminder of the monthly fee (DAS) appears.

When the data shows you already live the next step — you sent work to a workshop, opened a second shop, reached three people or are close to the free plan limit — Home shows the right plan once, with the price. It does not come back; Tenkai answers when you ask.

Resellers and shop owners open the bag page, enter their mobile number, confirm the code that arrives on WhatsApp and see, for each stall that uses Tenka where they bought, the orders, the purchases with the items, the trip reservations, what they still owe and the fair days. Each stall only shows what is its own, and no stall sees another. It is free. On the Balcão plan your stall already shows up; on other plans, turn on "Shows in the buyer bag" in Parameters.

In Company settings, Subscription tab, the account administrator accepts the terms and gets the referral link. When the new account created through the link pays its first monthly fee, you earn days of your own monthly fee and, after that, a share of every monthly fee it pays. The credit is deducted from your next invoices, and the card shows how much you have earned, how much was deducted and how much is still to be deducted.

Once your stall has had three weeks with sales, Tenka sends a single question on WhatsApp: from 0 to 10, how likely are you to recommend Tenka to another stall. Reply with the number (and anything you want to add). The answer goes straight to the people who build Tenka, and the question is not repeated.

On the Bus trips screen, register when your stall opens: the early-morning fair every Wednesday, the Saturday extra opening or a fair on a specific date, with time and place. The next days show up together with the bus trips, in your buyers bag and on the Home screen.

The buyer bag now has "My resale showcase": she picks the pieces she bought at the stalls, writes how each one appears, sets HER price and gets a link to send to her customers on WhatsApp. Whoever opens the link sees the photo, the description and her price — never the stall name, the cost or the wholesale price. She can create a new link (the previous one stops opening) or take the showcase offline at any time. It is free, like the bag.

When the requested piece is out of stock, the sales rep's phone (on the order line) and the phone checkout (on the sale line) now show when it will be ready — in stock, in production with the expected date or by the standard lead time — and whether the date was measured from the real production pace or estimated. It is the same date as in the sales order, the catalog and WhatsApp, with no cost or subcontractor name.

In Company settings › Subscription, the 24-hour salesperson card shows the price table by customers served in the month, how many the store has already served this month and the button to turn it on. The invoice charges the previous month's band, and the preview of the next invoice already shows the line. Without the 24-hour salesperson, a person from the store answers customers on WhatsApp.

Each clothing plan comes with a number of WhatsApp messages per month, shown on the plan card. At 80% the administrator gets a warning. Whoever uses the Tenka WhatsApp number (no own number) stops sending what uses credit at 100%, until buying a package or the month turns — replies to customers who wrote keep going out. With the store's own number, what goes over goes to the invoice, as before. The overage follows Meta's price table in reais.

In Settings › WhatsApp channels you can now save the Instagram page token (to answer Direct in the same service) without retyping the WhatsApp token, and choose, for each person with a linked number, whether they get replies also in audio, only in text or as the company set. The Tenka WhatsApp number, which serves several stores, is marked in the list.

Customer 360 has a new Buying profile tab: the customer's size by average-ticket band, how often she buys, the groups and items she buys most and what she asks on WhatsApp, with the source — nothing to type. The 24-hour salesperson uses the same profile to answer "what's new?" with in-stock items in her style.

Each store card in My stores shows, beyond the WhatsApp total, who in the store answered in the last 30 days: how many conversations, in how many minutes they replied and how many sales were born in the chat. In the anchor partner dashboard, each account shows its WhatsApp service and a table adds it up by the partner's salesperson — only for accounts that allow seeing their usage.

"Do you have a catalogue?", "what's new?" and "do you have 2050 in other colours?" now get an automatic answer: the catalogue, in-stock new items in the customer's style and the item's size grid. We measured with 50 wholesale-style conversations: 8 in 10 are answered without anyone from the store.

"How much is 1234?" and "price of 2050 from how many pieces?" now get an automatic answer: the wholesale price from your default price table (the same as the catalogue), the price by quantity and the item's closed size pack. It never shows cost or the price agreed with another customer. "Is 1234 back?" is answered like "do you have 1234?". If your store only gives prices to registered retailers, turn it off in Parameters, 24-hour salesperson: the question goes to a person from the store.

You can now ask Tenkai "which customers have no active contract?", "who bought in the last 90 days and has an overdue invoice?", "which items have not sold in 90 days and still have stock?", "which suppliers have we not bought from in 180 days?" and "which customers stopped buying?". Each answer brings the list with names that open the screen to check, and respects the companies chosen at the top and what your profile can see.

Tenkai now answers "how many yarn reports do we have?", "which bales came in this month?" or "what is the value of the lint contracts?" on almost every record and list screen, even those without a ready-made question. It finds the screen from your words, brings the total, the sum when you talk about value and up to 10 records with the link to each one, plus the link to the list already filtered so you can check. It only shows what your profile already sees on the screen, and hides amounts from those who cannot see amounts.

Screens that show numbers and that Tenkai could not read yet now answer in the chat: trial balance, journal, ledger, accounting income statement, balance sheet, value added statement and EVA; tax calculation and tax regime simulator; financial alerts, working capital, default risk, credit score, budget against actual and recurring revenue; sales dashboard, campaign ROI, white space and market; team capacity, flow metrics and requests dashboard; provisions, climate and SPICE; outsourced sewing plan and network; and the strategy dashboards. Ask the way you speak, like "does the balance sheet balance?" or "who is overloaded next week?". The number is the same as on the screen, only for those who can open the screen, and amounts stay hidden for those who cannot see amounts.

Personal screens also answer in the chat, always with what belongs to the person asking: what awaits your decision today, the daily summary (cash, overdue items and what to pay this week), your visit route, your profit sharing, your expense reimbursements, what you are accountable for and the partner portal. Screens that keep no numbers, such as wizards, settings and calculators, answer through the written help of the screen itself.

In the phone register, an item that is not registered can be sold by price alone: type "29.90" in the search and press Enter, or tap the tag next to the search and type the price (and, if you like, what it is). The sale is saved like any other, without creating a new item for each sale, and it is flagged for whoever checks the register.

With automatic Pix turned on, "sold 5 size runs of the ribbed top by Pix, I need the QR for Maria" is no longer refused: when you confirm, Tenka creates the checkout charge and sends the QR code and the Pix copy-and-paste code in the chat, for you to forward to the customer. The sale goes into the checkout by itself when the Pix arrives, and you get a message. Without automatic Pix, the sale is saved right away, as before.

In a WhatsApp sale, say "to be delivered on tomorrow's route": the delivery opens with the address on the customer's record and becomes a stop on tomorrow's delivery run (the one already planned, or a new one). If the customer has no address on record, the proposal warns you before you confirm.

Send an audio on WhatsApp or ask in the chat and Tenkai answers from your data: where your stock is and what it is worth at cost, who sold the most and which store or booth sold the most, what deserves reordering or production, which collection to invest in by trend, the best-selling days of the week, the customer and the products that brought in the most, and the bills overdue and coming due.

The partner representative gets a sales link: whoever creates an account through it counts as their sale. In the portal they register their own leads, which stay theirs for 90 days and renew with each logged visit, follow the accounts they sold and their invoices, see the expected commission of the month and the advance still to deduct, and request the monthly closing with one click.

On the expense contract record, the Requires Legal approval field comes switched on. Switched off, the payables are generated without waiting for approval. Only people with authority (edit permission on Approval limits) can switch it off; a contract Legal rejected cannot be waived and does not generate payables. Who switched it on or off, when, and from what to what is kept in the record history.

In the person's card under Access, the "Access active" switch turns off their sign-in: an open session ends within 30 seconds, the reason is recorded and the password does not change — turning it back on restores access as it was. The deactivated person stays in the list, marked "Deactivated".

In the price table, the Quantity tiers tab says from how many pieces the price changes (for example 1 to 11, 12 to 47 and 48 or more), with the tier price or a discount. The total of the style in the order counts, across all colors and sizes, and no tier goes below the channel margin floor.

In the portal B2B order, when calculating, each style shows the quantity tier reached and how many pieces are missing for the next one, with its price. The text order and the sales rep phone use the same rule.

In the contract with the company or school, the Uniforms tab keeps the kit for each role or grade and the named list with sizes and the name to embroider. Create order from the list adds up the sizes of everyone not yet served, saves the order at the contract price and opens the production order for what is missing.

On the portal, the company HR or the school office registers who joined, with role, sizes and name to embroider. The kit order for that person is created right away, at the contract price.

The sales order has the Sales channel field: wholesale, large retail, own store, e-commerce, marketplace or franchise. Orders from the portal, the sales rep, the marketplace and the online store arrive with the channel. Each channel share in a stock shortage now applies to real orders.

In the Price tables list, the Actual margin by channel box shows, for the last 90 days, each channel revenue, cost and margin after its fee, and flags the channel that sold below its margin floor.

A sales order with certified fiber (GOTS, GRS and others) now reserves the scheme balance: two orders cannot sell the same kilo. On the Transaction certificate screen, Request the order TC creates the outgoing certificate linked to the order, and the order invoice carries the TC number.

In the supply contract with call-offs, once set, the volume changes through a volume amendment with number, effective date and reason, kept on the Amendments tab with the volume before and after.

When you record the delivery of a contract call-off, the sales order is created at the contract price, leaves stock and is billed with the invoice and the receivable. If something is missing, the screen says what and the order stays linked to the call-off to finish.

In a license with a licensor abroad, enter the contract currency: the minimum guarantee and the per-piece royalty turn into reais at the day rate (with no rate, the system does not close). Booking the minimum and closing the statement create three payables: the net to the licensor, the withheld income tax and the CIDE on remittances, the last two paid by DARF.

From this version on, every new company starts with the refusal of outflows without stock turned on: nothing leaves stock leaving a negative balance without an authorization in the Stock panel. Existing and demo companies stay as they were; anyone can turn it on in Parameters, Production group.

When the contract customer has portal access, the volume or price amendment awaits their acceptance: the contract only changes after they accept it on the contract page in the portal. If they decline, they give the reason. Who decided, when and from where is recorded, and you are notified in the bell. If they accepted by e-mail, confirm on the contract with the evidence.

In the supply contract with call-offs, the price adjustment is a price amendment with the date from which it applies. Each delivery is billed at the price in force on its date, deliveries already billed do not change, and the price history stays on the contract page.

When a contract call-off delivery does not reach the invoice and the receivable (missing item or price, shipping or billing fails), whoever bills gets the alert in the bell and the contract list shows the board of unbilled deliveries, with the reason. The delivery leaves the board and the bell once billed, from the call-off or from the order screen.

Those who sell uniforms to companies and schools get the Academy path "Uniforms — from the kit to the embroidered name": the kit per role, the list of who wears it, the order that comes from the list, the replacement through admission in the portal and the embroidered name. It appears when the first kit item is saved, and the same five steps are in the help of the contract screen.

When a needle breaks while sewing, the supervisor records on the bundle the machine, the operation and whether the parts were recovered. Without the parts, the bundle goes into quarantine and the pieces stop until they pass the metal detector. The needle replacement is recorded with the old needle returned — replacing without returning the old one also quarantines the bundle.

Mark the garment audience (baby or children) in the Textile tab of the item. The shipment of that garment shows the metal detector box: each pass records the batch, the equipment, the pieces and the result, and the shipment only goes out when the passed pieces cover the picked ones. It is the record the retailer audit asks for.

Knit that comes back wet from the dye house weighs right on the scale and is short in reality. Now, on the shipment record, the moisture measured when it leaves and when it returns gives the conditioned weight on both sides; Tenka compares what left with what came back plus the declared loss and, above the company tolerance, opens the weight claim to the subcontractor with the missing kilos.

The company can turn on "refuse outflow without stock in every flow": the till, shipping, production, cutting and manual entries stop taking out what is not in stock, except with an authorization granted in the Stock dashboard (item, quantity, reason, valid for 24 hours) — whoever authorized stays on the movement. Turned off, operations do not change, but each outflow without stock and each zero-cost outflow shows flagged on the dashboard.

On the shipment record, the Return invoice tab matches each return with the invoice the dye house or the sewing contractor sent — picked from Received invoices or typed —, with the input CFOP (1902) and the processing CFOP (1124/1125). Tenka checks the input amount against the cost of what left in the shipment and the service against the return cost, and warns when they differ. Subcontracting also shows the shipments close to the return deadline.

Whoever opens a weaving or dyeing account no longer lands on the garment path. Weaving starts at the loom dashboard and goes through article, warp beam, shift output and inspection to the finished roll; dyeing starts at the lot and goes through recipe, lab dip, restricted chemicals, scorecard and invoicing. Every screen on the path has a three-step guided tour.

In the batch, choose continuous mode and enter the process (pad-steam, pad-batch or thermosol), the line speed, the pick-up and the liquor left in the trough. Weighing calculates auxiliaries from the liquor the fabric took, the time comes from the meters, and the panel splits water, energy and cost per kg between continuous and exhaust.

A yarn-package batch asks for the number of packages and the kg in each, which must match the batch weight. Once the color is approved, the Dyed yarn tab issues the grey yarn and receives the dyed yarn with the same lot and the batch cost added.

In the dyehouse panel, the Dyes and chemicals for the queue section adds up the recipes of the batches scheduled for the next days, compares them with stock and with what is already on order, and shows what is short, when to order and which batch runs out. One click creates the purchase order.

In the export process, the Export tab links the load’s packing slip and creates the invoice (from the items and the incoterm), the packing list (from the packing slip, with the same packages and weight) and the draft certificate of origin by HS code, as PDFs in the customer’s language. The export declaration number and its confirmation are recorded there and close the export.

The Drawback screen now counts as proven only exports with a confirmed declaration. What was exported without confirmation still counts toward the commitment, is highlighted on the act’s row and does not reduce the balance to prove.

Your cutting system, carrier and retailer can now read rolls, lots, shipments to processors, production orders, tech sheets and cutting tickets from your account — only what changed since the last read. They can also open a roll shipment and post production without duplicates when the network repeats the request. The key only reads what its owner can see in the system.

Ask "which of Dona Marta’s advances are open?": Tenkai lists each cash advance and trim advance not yet deducted, with date and amount, including the balance left from an advance deducted in part, and the total per subcontractor. And "how much subcontractor INSS do I have to pay?" brings the INSS, IRRF and ISS withheld on the receipts and the employer INSS still open, with the next due date.

The owner’s strip on Today now shows open retailer fines, subcontractors rated D or E, how much is still available to buy in the collection and machines with a predictive alert. Each number opens the list that adds it up, and only appears to those who can open that list.

On the "How much can I buy" tab of the collection plan, save OTB revisions with a scenario (base, optimistic or pessimistic), the reason and, if you want, a % adjustment. Each revision has a number and date and never changes; compare two of them, or one with the current OTB, category by month. The collection’s demand forecast appears in its own table, at average cost, separate from what has already been paid.

In the uniform contract, choose the lettering design on the piece that has the name embroidered: each name on the list shows the estimated stitches and the embroidery cost, and the tab adds up the cost of all. In the embroidery shipment, choose the contract: the shipment record gets the Names to embroider tab with the list, to send to the embroiderer with the pieces.

On the Cutting order, in the broken needle panel, the Policy report as PDF button gathers the summary, the broken needles and the metal detector passes of the period. Choose the retailer and the PDF comes out in their language; with no customer, in the company language.

In the Textile chain map, the new Monthly close in kilos section shows, for each group company and its link (spinning, knitting, weaving, dyeing, apparel), the opening stock, purchased, produced, sent to and returned from the third party, sold, waste, declared loss, expected and book closing stock, and the difference nobody explained, in kg and %. Closing the month freezes the numbers and that month stock no longer accepts movements; reopening is for whoever administers, with a reason.

An administrator can load an A1 certificate for that register only, right in the POS. Invoices issued offline are signed with it, and the company certificate no longer leaves the office. Without it, the register shows a red warning and reserves only a few numbers.

In the phone register Menu, "Offline invoice": an administrator approves the phone and loads a certificate just for it; the operator prepares it with their own password. If the internet drops at checkout, the invoice is signed, carries the contingency banner and uploads by itself when the network returns.

The customer paid a Pix above the amount: the sale closes at the charged value and the difference becomes her credit for the next purchase. With no customer on the sale, the register shows how much to refund. Whoever manages the register gets a bell notification. Applies when the account's Pix billing is connected.

When closing with a self-employed receipt, what was withheld becomes three payables, to social security, the federal revenue and the city hall, each with its due date: the 20th of the following month and, for service tax, your municipality's day.

In Received shipments, "Bill and issue the invoice" creates the receivable from the garment maker and opens the record, where the service invoice goes out through your tax provider.

A small garment maker opens without spinning, knitting, weaving, dyeing, the supply-chain cockpit and large retail in the menu and search. Nobody loses access: the screen opens by its address, with the "industrial mode" notice.

Each person chooses for themselves, in the avatar menu, between seeing everything and seeing the essentials. It applies in this company and overrides the company choice.

In Company settings, Identity tab: Automatic, Essential or Complete, with a sentence on what Automatic decided and why (entry plan, a company that spins yarn, industry module in the plan).

In Production, Cutting plan, choose the retailer order (or the production order), the style and the fabric: Tenka combines the CAD markers and the rolls in stock and tells you how many plies of each marker to cut, in which shade band and with which rolls, using the least fabric without missing pieces. The calculation is explained.

Once the plan is approved, each lay becomes a cutting order with the rolls the plan chose. The rolls of an approved plan are reserved and do not enter another plan.

Connect the folder where Audaces or Gerber export the marker report: every 5 minutes Tenka reads it, stores the marker with the pieces per ply and takes the consumption to the tech pack. The same file read again does not duplicate; a file that won't open goes to the "error" folder with the reason.

Lectra connects through the API, with your Lectra access user and password. Until the credential is registered, the connector stays in demonstration mode and says so.

Each proof of the garment's origin (bale lab report, cutting, shipment to the contractor, surprise visit, destination of unsold stock, fibre certificate) is recorded in a chain where each proof carries the mark of the previous one. The public passport shows the chain and a "Verify now" button: if someone tampers with an old proof, the page says at which step the chain broke.

New "Transaction certificate" screen: record the GOTS, GRS, RCS, OCS or BCI TC that arrives with the fibre and see the balance you can still sell as certified. A sale above the balance, with the supplier's certification expired or with a lot not traceable to the bale is rejected, with the reason.

New "EDI with the retailer" screen: the large retailer's order arrives through the VAN and becomes a sales order by itself every 15 minutes, once the VAN is contracted and connected. If any barcode (GTIN) in the order has no colour and size of yours, the order does not come in half: it appears in "GTINs blocking orders", you say which variant it is and it comes in whole.

The shipping notice comes from the checked dispatch, with the SSCC of each box and pallet, and the invoice comes from the authorised tax invoice. Both go to the VAN and become "Confirmed" when the retailer replies.

In Print design, the "Digital" tab stores the design's print profile: the ink of each colour (cyan, magenta, yellow, black and extras) per metre, the machine time and, for sublimation, the paper. The cost per metre is calculated, and when metres are reported on the production order the ink leaves stock by itself.

The seamstress can only report the bundle ticket after supervision approves the first piece of the operation: green releases, yellow releases with a warning and red blocks and opens an in-process inspection. It applies on the phone, at the workstation and offline.

In the collection plan, the Forecast tab now has a statistical forecast per item: how much it should sell in the coming weeks, the minimum and maximum, and the measured error. An item with less than 8 weeks of sales shows "no history", and the system does not make up a number. Test and replenish does not restock above the forecast.

In the Dyehouse panel, the Laundry section: wash recipes (enzyme, stone, ozone, laser, softener), the batch that weighs the chemicals and deducts stock, and the closing with shrinkage, right first time and cost per kg. An outsourced laundry goes through the shipment.

In Bale, the "ID and QR" tab generates the permanent ID (the ABRAPA code or the company's SSCC) and the QR label. Whoever scans the QR sees the HVI report, the fibre origin and the bale's chain of proof; at receiving, the phone finds the bale by its QR.

When two batches of the same colour fit together in one machine, the dyehouse schedule shows "Combine into one bath": the first batch takes the kilos of both and the other goes to the recycle bin with its trail. Only those who can edit the dyehouse panel can combine.

New "Productivity benchmark" screen: record kg per spindle per hour and your mill's CVm and IPI alerts for each process and count, starting from the market reference. The machine monitor and the barré risk now use yours.

Once the surplus is delivered, "Receive into stock": choose the item and warehouse, and it comes in with the source lot and, if sold by kilo, with the roll it came from.

The garment's public passport shows the whole chain of proofs: the bale, the yarn lot, the knitted fabric, the dye house, the cut, the sewing contractor and the finished garment, even when each step was done by a different company in the group. "Verify now" rechecks all of them: if a proof further back was tampered with, the page says at which step the chain broke.

On the sales order, a line can be marked as a certified sale (GOTS, GRS, RCS, OCS or BCI) with the lint lot the fibre came from. If the quantity exceeds the certificate balance, the supplier's certification has expired or the lot does not trace back to the bale, the order is not saved and says why.

On the retailer EDI screen, the real VAN fetches the orders and delivers the shipping notices and invoices to the provider's folder. Enter the address, the user and the password (or the private key the provider gave you) and the server key the provider confirmed: without it Tenka does not connect, so it never talks to a server pretending to be the VAN.

In the collection plan, the statistical forecast has a new "By size and colour" column: when store sales and orders carry the size grid, each size and colour gets its own forecast. A size that started selling less than 8 weeks ago shows "—": the forecast does not split the item's total to make numbers up.

On the Drawback screen, each act shows what came in with suspended tax (in kilos and dollars), what exports have already proven, the balance still to prove and how much of the suspended tax is still open. If the act expires with a balance, the open part shows as due.

In the foreign trade process you choose the regime. Under drawback, federal taxes are kept as suspended and do not enter the fibre cost. Under ex-tariff, import duty is calculated at the reduced rate.

In the tech sheet, register the embroidery design with its stitches, thread changes, machine speed and cost per thousand stitches. Choose the design on the embroidery step and the garment cost shows embroidery on its own line.

In the subcontracting shipment, choose the Embroidery type and the design that goes with the pieces. On return, the loss is declared as with sewing subcontractors.

In the price list, set for each channel (wholesale, sales rep, own store, marketplace, large retail) how much it adds on top of cost, the fee the channel takes and the minimum margin. "Generate from piece cost" calculates prices from today's cost in the product sheet. When sewing or fabric costs rise, the price list page shows which channel fell below the minimum margin and the price that brings it back to the floor.

A roll that inspection grades as second quality moves on its own to the second-quality stock, with its cost. Price lists now have a quality and the channel "Second quality (outlet, bazaar, end of stock)". In a sales order, a piece coming from second-quality stock in a first-quality order shows a warning and only goes through when you save again to confirm. Ask Tenkai for the margin of first and second quality.

Knit cut right after unrolling shrinks after the garment is done. Now the knit article says how many hours the roll rests before spreading, the lay in the cutting plan marks when the rolls were unrolled and shows how long is left, and the cutting order warns about (or blocks, if the company prefers) a roll that has not rested yet.

On the rolls screen, a yarn package gets the measured moisture and the conditioned weight at the official regain of the fibre (blends by composition). The invoice carries the three weights: scale, moisture and conditioned. The buyer checks it at receiving against the invoice weight; a difference above the tolerance opens a weight claim to the supplier.

A fabric roll shows the metres expected from its width and weight per m² and, once measured, the real metres per kilo. The rolls screen compares expected, measured and agreed yield by supplier, article and lot; fabric that yields less than agreed opens a claim to the supplier.

In the batch, "Release weighing" shows what to weigh and takes the chemicals out of stock. Bath corrections go in as additions, with reason and who authorised, and add to the actual cost.

Export the batch weighing to the dispenser and import what it weighed: the deviation shows per product and stock adjusts. It works with the dispenser file in the accepted format, described in the screen's help, and the file is checked in full before saving.

Record the customer's colour request and trials A, B, C read in daylight, store light and incandescent light. The system flags the one that shifts with the light, and the approved one becomes a production recipe without retyping.

Every measured roll gets its 555 shade band, and cutting does not let you spread rolls of different bands: pieces of the same size run come out the same colour.

The dyehouse screen shows what each machine is dyeing and what comes next, and schedules the queue within each machine's kg, light to dark, washing only when needed — in a Gantt of the next 48 hours.

Record each finishing pass of the batch with the machine settings, the weight in and out and the predicted shrinkage next to the measured one. Weight that does not balance is refused.

Register the design, the colours with their flat or rotary screen and the paste. Production is only recorded with the customer's approved strike-off, and the screen warns at 90% and 100% of its service life.

Each chemical against the ZDHC list: a blocked one can no longer enter a recipe, weighing or addition, and the safety data sheet stays attached. The screen shows the treatment plant's 12 months, with water per kg and COD against the limit.

You can now register denim, twill and plain weaves with the weave, number of ends, ends and picks per centimeter, reed and greige width, weight and selvedge. Tenka checks that the number of ends matches the density and width. And each yarn in the style's recipe says whether it is warp or weft.

Each beam keeps meters, ends, breaks, the lot of the yarn that came from the spinning mill, the size recipe, declared and real pick-up, sized weight, indigo and shade. The yarn leaves stock with its lot, and a sizing that weighs more than the yarn plus the declared size is not accepted.

The Weaving mill screen shows, for each loom, how much warp is left and in how many hours the beam runs out, with a Change beam button. The change keeps the standard and the actual time, and the screen shows how much longer changes are taking than the standard.

Register the weaving looms with their speed and record each shift with picks and stops. The screen compares looms by warp and weft stops per 100k picks — high warp stops point to weak yarn or weak sizing.

Each piece off the loom has a number, loom, warp beam, meters and weight, and the 4-point greige inspection already says whether it is first or second grade. The piece enters stock with its meters and grade, and a beam never yields more fabric than it had.

The warp beam says whether indigo was rope or slasher dyed, with the dye lot — and, for rope dyeing done outside, the shipment to the contractor. The screen warns when the shade jumps from one beam to the next on the same loom beyond the style's tolerance: that is where another shade lot starts.

The textile demo group now has eight companies: Demo Tecelagem makes denim with yarn bought from Demo Fiação (its lot goes on the warp beam), has twelve months of beams, looms, greige pieces and indigo, and joins the group chain cockpit as one more link.

Register feeders, stitch length, speed, revolutions and roll weight: the machine shows its needles, minutes per roll and kg per day at 100%. Needle changes have a date and an interval, and overdue ones light up.

Defects with code, severity, points and probable cause, in one catalog for knit, woven, yarn, sewing and garment. The inspection records each defect at the meter where it is, and the screen shows the Pareto by machine.

Record in the test what went greige to the dye house and what came back finished: the screen shows weight loss and fabric weight and width deviation against the forecast, by article and dye house. Finished heavier than greige is refused.

Import the spindle sensor file and see the spindles breaking twice the machine average. One click sends the maintenance order with what to check. You can try it with a simulated reading before connecting the device.

Keep speed, twist, draft, ring and traveller for each yarn on each ring frame and lot. Best practice comes from the lot with the best report, and a new setting that drifts from it warns at the lot change.

By yarn lot, the lab report next to what the fabric showed: yarn defects, points, pilling and barré, with the barré risk from CVm and IPI. It is clear when the report warned and the fabric confirmed.

Each ring frame and yarn in kg per spindle per hour against the count reference. What is below 90% shows first, and the reference can be your own plant’s.

You measure one size, say how much each point grows per size and Tenka builds the whole table, with the point code and the right way to measure.

Proto, fit, pre-production and production sample: you measure, anything over tolerance turns red, photos stay together and the customer approves through the link, spinning the garment in 3D.

Each collection and order has its milestones, planned × actual. A late milestone pushes the delivery, the screen shows the new date and which milestone is holding it, and you are notified.

Price, minimum order, lead time and certificates for each supplier, with the cheapest and fastest marked and the expired certificate highlighted. The preferred one is used in the sheet cost.

One tap on the sheet pulls the imported marker: the base size becomes the fabric quantity and each size gets the factor used by cutting. No more guessed consumption.

The cut becomes packs by size and color, with plies, roll and a QR label. The sewer scans the QR on the phone and clocks the operation; on the Cutting order you see how much of each pack is in each operation.

Meters out of the roll against the marker consumption and the pieces cut: the waste shows up, a roll over tolerance turns red and the end piece goes back to stock with its measured length.

The new operations library keeps the standard time of each operation by machine type. On the sheet you choose the operations, Tenka adds up the minutes, works out the cost and saves the target cost to compare with the actual.

On the phone, enter the lot size: Tenka says how many pieces to check and how many critical, major and minor defects the lot can have. The verdict comes from the standard and is recorded with the photo.

On the phone, inspection defects are those of your catalog, with code and severity. In the final inspection, critical, major and minor come from the catalog — the lot verdict no longer depends on counting from memory — and the photo stays on the defect it shows.

The Quality tab of Produce right shows what causes the most defects in inspections — by process (sewing, finished garment, dyeing, finishing) and by subcontractor or supplier — and what to tackle first. When the dyed roll arrives, the defect is also picked from the same catalog.

When orders exceed stock, Shortage allocation shows who gets what by customer priority, complete orders first and date. You keep a share for e-commerce or the marketplace without moving goods, check the simulation and only then apply it.

In the packing list, the new tab numbers every carton and pallet with the SSCC large retailers scan at receiving, prints the GS1-128 labels and generates the shipping notice already checked against the order. A notice with discrepancies is not sent until the cartons match the order.

Every debit the retailer deducts becomes a record with cause, reason and the receivable it reduces. You dispute it with evidence, accept it (with approval limit: it becomes an expense payable to the retailer, flagged to be offset against the open receivable up to its balance) or record when it is refunded. The top of the list shows the Pareto by cause: where the factory loses the most money.

The contract gets the total volume, the item and the price. Each delivery call-off draws from the volume and Tenka shows what was called, delivered, still to deliver and the balance to call — and does not let a call-off exceed the balance.

In the product's passport tab, Tenka adds up the spinning energy and the water, steam and energy of dyeing and weaving measured along the chain down to the piece. Each value says whether it was measured (verified) or came from the reference (estimated). One click puts the footprint in the passport and in the QR.

The product passport shows, field by field, what the EU textiles delegated act will require and what you already have: identification, composition, recycled content, who made the fabric, footprint, repairability and the evidence. What the EU has not defined yet shows as "to be defined". The map is open data through the QR.

On the ESG screen, the environmental self-assessment answers the numeric questions of Higg FEM and Green to Wear with what the factory already records — measured energy, water, steam, production, loss and dye lots — saying for each whether it is measured, estimated or missing. Export it and send it to the customer.

In the shipment to the subcontractor, record the unannounced visit: Tenka brings what should be in production, you count what is on the table and note what is not in the shipment (another brand's production or passed on). The visit closes as compliant or discrepant, with the findings.

If your factory already has equipment that reads the machines (the maker's server or a data-collection program on the network), it can send each machine's state and output straight to Tenka, in the accepted format and with a password that belongs only to your company. Repeated readings do not duplicate and wrong ones come back with the reason. The step by step for whoever runs the network is in the implementation guide.

A new tab in the Machine monitor shows every machine in spinning, knitting, weaving and dyeing by state — running, stopped, no program or under maintenance —, for how long, the stop reason, how much they ran today and the cell's OEE. You see at once where the factory is losing time.

In the phone's Shop floor, the Machines now card lists the stopped machines. The operator picks the machine and the reason — out of yarn, breakdown, style change, maintenance, cleaning, quality or no operator — and the office sees it right away in the Machine room.

When the equipment that reads the machines goes 24 hours without sending a reading, or a sent trade bill goes 48 hours without an answer from the registrar, Tenkai opens a stopped-integration alert.

In Test and repeat you launch the test batch, see sales by channel (live, website, pickup, store) and Tenka drafts the repeat. It only becomes a production order when you confirm; missing fabric becomes a purchase request and the sewing goes to a subcontractor with free capacity, with a deadline to answer.

The contract with the licensor gained the License and royalties tab: minimum guarantee as payables, royalty on sales with returns reversed, artwork approved by style, numbered seals and the report to the licensor. The License royalties screen shows how much you owe each one.

When the Network exchange is active on your account, free loom and sewing hours circulate between the network's companies (your group and, if you open it, the accounts of the anchor partner's network), without the offerer’s name until acceptance. The contractor sends the shipment for processing, as always; reputation only shows if the company chooses to publish it.

When the Network exchange is active on your account, offcuts, roll ends, idle yarn and unsold stock go into it with weight, count, lot and origin. The buyer inherits the lot; the sale goes out with an invoice, and between companies of the same group the amount counts only once.

The maintenance screen has a new Predictive section. With the equipment that reads the machines' vibration and current connected to Tenka, the first month builds the baseline and, after that, once the plan's threshold is crossed, the maintenance technician gets the order before the breakdown.

New Defects seen by the camera screen: when the loom has an inspection camera and the supplier's equipment connected to Tenka, what it flags arrives with the fabric crop, the roll and the position in metres, linked to the defect catalog. The inspector confirms or discards, and the crop is deleted after a short period.

When the Night production planner agent is switched on for your account, the dyeing machine and loom sequence is redone overnight and waits on the schedule screen and in the Inbox. You confirm or discard; if the customer deadline changes, sales confirms before any conversation with the customer.

In Advance receivables, a receivable backed by a firm customer order becomes an electronic trade bill in one click, with the order as collateral. Registration and the advance come with the regulated credit partner: with one, you advance seeing the cost in three parts; until then, you see what it would cost.

In Own credit score, each contractor gets a score from 0 to 1000 based on deadlines, losses, late shipments and expired documents — using only what you recorded with them. You see the facts behind the score and anyone can request a review. The score informs; it blocks nothing.

The IBS/CBS Simulator now has tax reform by link: from cotton to store, year by year until 2033, the new tax, the shrinking ICMS, the state incentive that ends with it and what split payment withholds. Compare staying, relocating and outsourcing. Each rule shows the law it comes from.

The collection plan now has the Open to buy tab: you split the budget by category, month and store with a target margin, and see side by side what was budgeted, what is already in purchase and production orders and what has been paid — and what is left to buy.

Keep the fibre origin report (isotope, DNA or documentary) on the bale, with the document. The garment passport shows the origin as verified only when every bale has a confirming report — one bale without it leaves it estimated.

In What to mark down, the Unsold stock destination tab records donation, resale and recycling with each one’s proof (receipt, invoice, manifest with the weight) and shows what is still pending — what the European rule against destroying stock asks of whoever sells in Europe.

The new Textile EPR by country screen keeps the fee each country charges per piece or per kilo, with source and date, and calculates what you exported in the period, country by country. A country without a rule shows as pending.

In the subcontractor record, the Due diligence tab checks every month the company registration status, the Labour Ministry employers list you import and the ABVTEX audit. If something comes up, whoever approves limits decides to block or release the next shipment — and only your company sees the result.

On the environmental licence and the water permit, register the conditions: what to measure, what to deliver and when. The measurement reads the latest treatment-plant reading against the limit, and the alert arrives before the due date.

Register the union’s collective agreement with the floor and the source. Switched on, the CLT seamstress’s output gets the top-up to the floor and weekly rest pay on output, each on its own payroll line — and does not close without an agreement in force.

Tenkai now answers "is a store transfer on the way?", "how much went missing in the counts?", "has Maria's shipment arrived?" and "how many paid by Pix in today's live?", with the link to the screen each number came from.

Retail, distribution and wholesale, and B2B consulting and services businesses now have their own "First 30 days" track in the Academy, with the lessons in the order the work happens.

Once your company's digital certificate is in Tenka, NF-e and NFC-e invoices go from Tenka straight to your state's tax authority (SEFAZ), with no company in between — this path is ready to switch on and being certified with SEFAZ. A rejection comes back as a sentence saying what to fix. Until then, the invoice comes out as a demo and is marked that way, never as authorized.

The Tax setup assistant asks for four things: the state, the tax regime, the NFC-e security code and the digital certificate. The state's rule is shown alongside (the amount from which the customer ID is required, the register invoice limit, whether offline mode is allowed) and at the end Tenka tests the connection with SEFAZ.

With your company's certificate in Tenka, the contingency consumer invoice is ready to switch on (being certified with SEFAZ): with no internet or with SEFAZ down, it prints with the contingency stamp and is sent when the connection returns; after more than 12 hours unsent, the team and the owner are warned. Issuing at the register itself with no internet only after the administrator approves that register. Without the certificate, the sale is saved and the invoice is issued when the connection returns.

Once your company's certificate is in Tenka, a register purchase with a company tax ID or above the state's travel-invoice amount becomes an NF-e on its own, with the customer's address and the right in-state or out-of-state operation, without leaving the screen — ready to switch on, being certified with SEFAZ. Below that amount, the consumer invoice with the personal tax ID applies. The register warns before charging.

The register invoice comes out at 80 mm and the NF-e on A4, as PDF, and goes by e-mail or WhatsApp with the invoice file, in the customer's language. At the register, the last sale's receipt has the Invoice by WhatsApp button; on the outgoing invoice, Download and Send to customer.

Once your Stone or PagBank card machine and your Asaas account are connected by BMCode, card and Pix also close the sale on their own; until then, the Phone register already sells in cash with change, store credit, voucher and Pix you check yourself. It opens fast even on a basic phone with a weak signal: scans with the camera, searches by voice, builds the size grid and charges in three taps. With no internet it keeps selling and shows how many sales are waiting for the connection. In fair mode, three big buttons, and the wholesale price kicks in by quantity.

Once your Stone or PagBank card machine is connected by BMCode, the amount goes to it (through the Tenka app on the terminal or the counter register's PIN pad) and the approval comes back to the register and settles the sale, with the receivable and the card brand fee — ready to switch on, being certified with each card machine. Tap-to-pay on the phone itself follows the same path. Until then, card payments work as today, on the machine you already use.

Once the store's Asaas account is connected, the register shows the Pix QR code with the amount and the sale closes when the payment arrives, without checking the bank app — ready to switch on, being certified. After the deadline, the charge is cancelled and the register warns you; a Pix that arrives after the deadline shows up in the bell with what to do. Until then, the register shows the QR code of your Pix key and you confirm receipt.

On the style you set how it sells wholesale: the multiple that closes the size grid, the minimum per style and the wholesale price from N pieces; the store can have a minimum order. It applies at the register, in the catalog, the portal, the sales rep app and WhatsApp: the screen says how many pieces are missing to close the grid, and whoever has approval authority can release it.

At the register: CPF, name, city and WhatsApp, and she is already buying. A CPF that already exists finds the record instead of duplicating it. When the customer is picked, the register shows the last purchase, what she took and the available store credit. With the Federal Revenue base loaded, the name and city of a micro-entrepreneur reseller come from the company tax ID.

In Excursions you register the trip (agency, guide, city, bus, date, seats) and the resellers who came. The register links each sale to today's excursion, the packages come out labeled with name, city and seat, the guide's commission becomes a payable, and the guide gets the statement on WhatsApp and a link with their resellers.

In Shipments, the sale becomes a shipment by carrier, bus ticket office or post office, with labeled packages and tracking. Each status change (posted, in transit, arrived at the office, delivered) prepares the message to the customer on WhatsApp; you are the one who sends it.

An order can be marked for pickup at the stall on the excursion date: the store picks it and the reservation expires on that date. At the register, the order search accepts the reseller's CPF and brings pre-reservations first. After the date, the order goes back to quote and the stock is released.

One card per store, side by side: today's sales, number of sales, average ticket, register open since when, the salesperson against her target, stock about to run out, pending invoices, today's excursions and what is on the way. It refreshes every minute, has a TV mode and tapping a card opens the store. The monthly target is set right there.

In My stores, each store's result for the month (revenue, costs, margin, fixed expenses and result) and the group's, which is the sum. Rent and staff that one company pays for all are allocated by each store's revenue or in equal parts, without changing the total.

My stores gets the Sewing workshops block: how many pieces are out, late shipments, when each one comes back (what the workshop reported on the link counts more than the agreed date) and how much to pay each workshop this month.

In Transfer between stores you scan the pieces or accept the suggestion based on what sells most at the destination, send them with a packing list and package label, and the receiving store checks them by scanning. Whatever was missing or extra becomes a pending item that only closes with a reason.

The website or channel order looks for the group store that has the piece: first in the customer's city, then the nearest one, then the one with most stock. The store picks it on the phone, ships it or hands it over checking the CPF; one order can be partly shipped and partly collected.

Stores marked as "sell online" are counted in the channels' available stock, minus what is reserved. If the register scans a piece reserved for an order, it says whose reservation it is and how much is still free.

In Scheduled count you set, by store and product group, the weekday of each count. On the day, the salesperson counts on the phone by scanning with the camera, sees what is left to count and applies it with the reason for the difference. My stores shows today's count and the difference over the last 90 days.

Once each channel's seller account is connected, Shopee, Shein and TikTok Shop work like Mercado Livre: the order arrives on its own with the right variant, stock is updated, the shipping label is generated and, with "issue NF-e" on, the order's invoice is created as a draft. All three are ready to switch on and being certified with each channel; an order already paid on the channel is never blocked by the wholesale closed size grid.

To take Pix and card payments in the online store, the store's Asaas account must be connected; with it, Tenka's retail store goes live: retail price, a single item already sells, photo per color, size chart from the spec sheet with "how to measure", cart with personal tax ID, shipping by table or pickup, and your own domain if you want. No fee per sale; once paid, the order goes to picking.

For the live's Pix queue, the store's Asaas account must be connected. The online store's live mode has a single link, live stock and a few-minute hold: two customers never take the last piece, and anything unpaid goes back to stock on its own.

Through the order link, the customer picks the piece that goes back, the reason (size, color, defect), whether she brings it to the store or ships it with the label, and whether she wants a voucher or another piece. The store checks and completes it in one click: the piece goes back to stock, the voucher is created and arrives on WhatsApp, and the return invoice is created as a draft.

The online shop publishes two catalog addresses, one for the Instagram and Facebook shop and one for Google, with price, unified stock and the photo of each color. The product link leads to your online shop. You just paste each address once.

The size-grid form and the payment link in the chat depend on the store's WhatsApp number with messages approved by Meta and on a connected Asaas account — ready to switch on. With them, the customer asks for the catalog or picks size and color, the order is created as a quote for the salesperson who serves her, the salesperson confirms in one tap and the link (Pix or card) goes in the same chat. "Do you have BV-2210 in M black?" is answered from the grid stock.

In WhatsApp usage: what the company used this month by message type (service, notice, access code and marketing), the plan allowance, the package balance and what goes to the invoice. You can buy +1,000, +5,000 or +20,000 credits. Marketing without balance is blocked with the reason; customer notices continue and go to the invoice. The warning arrives at 80% and 100%.

Once BMCode switches on the on-model photo service for your account, Tenka turns a photo of the item on a hanger or table into a photo of it worn by a model, one per color in the grid — ready to switch on, being certified. The photo carries the "AI-generated image" mark and only goes to the store, the catalog and the listing after you approve it. The cost of each image comes out of the Tenkai allowance and is shown beforehand.

With Tenkai switched on in your account, it writes the title, description and attributes for the online store, Shopee, Mercado Livre, Shein and TikTok, within each channel's limits, from the label's fiber content, the spec sheet's measurements and the care instructions. It never makes up fiber content: text that mentions another fabric or another percentage is rejected. You review and approve in one tap; publishing on each channel depends on that channel's seller account.

Customers to contact today brings the day's list ready: who has not bought in 60 days, who has a birthday, the color the customer wanted that arrived, the abandoned cart and the new collection for those who bought the previous one. The salesperson sends in one tap, only to those who agreed to receive messages, and sees who came back and who bought in the last 30 days.

Sewing workshop with an individual CPF: the closing calculates the self-employed receipt with social security, income tax and service tax by the current table, the payable is created for the net amount and the receipt goes as PDF on WhatsApp. On the portal, the workshop reads "you don't need an invoice, here is your receipt". Reporting to eSocial and DCTFWeb stays with the accountant, as the receipt says.

In production payment, record the cash advance or the trims you sent ahead. At closing, whatever is open is deducted from oldest to newest, up to the service amount, and shows in the calculation breakdown; the workshop sees the statement on the portal.

When closing a micro-entrepreneur workshop, the draft of the national service invoice is created: customer, "sewing service, batch N", period and amount. On the portal, the workshop sees "your invoice this month" with the National Issuer button and reports the number back.

Through the portal link, the workshop returns item by item, with the loss, the reason and the invoice number. If the workshop also uses Tenka, shipments arrive by themselves in Received shipments and she returns them there. At the garment maker, "The workshop returned, check" in Outsourcing opens the return already filled in.

In Workshop plan, each workshop's capacity per operation (pieces per week, lead time and price per piece) and the plan for the next six weeks, with what it already has and what is left. On a new shipment, "Which workshop takes it?" suggests who delivers on the date and shows the "what if": how many more days and how much more or less per piece.

In Workshop network you search, among the workshops in your partner's network, who has free capacity by operation, city and rating, request the sewing (it becomes a shipment) and rate from 1 to 5 on return. The workshop publishes its own capacity from its account or through the link. In this phase there is no payment guaranteed by the network, and the screen says so.

What to mark down shows, by style and store, how many weeks of stock remain at the current pace, how much of the collection has sold and how long the piece has been sitting. The suggested discount never goes below cost plus the minimum margin; in one tap it becomes a clearance in the price list, and the Marked down tab shows whether the piece started selling.

In Style from photo you take a photo of the piece and Tenkai suggests name, category and colors; the house size grid comes from the category. You check, set the retail and wholesale prices, and the style is created with its variants, a barcode for each and the labels as PDF. When Tenkai is unavailable, the screen says so and the fields are left to you.

On day 1, the accountant receives by e-mail the link to the previous month's folder: issued and received invoices, cancellations, sales by operation and by store, the Simples base, workshop receipts and card machine statements, plus the pending items (contingency invoice not sent, invoice without CPF). In the Accountant kit you can open any month and send the link right away.

A nota na feira, o ônibus chegou, vendendo pelo Zap, foto no modelo e o que remarcar: cada lição pratica numa tela nova desta versão.

Each vertical now has its own implementation guide in the Help Center, built from the modules it uses and the country: which screen, in what order, what to check, who does it and how long it takes — one step per screen, no repeats. At the top of the guide, each module says whether it already works in Tenka, works by connecting to your system, or is coming soon.

The Implementation Journey now shows your plan: the steps for your vertical, your account modules and the company's country, with a button to open each screen. Steps for customers, suppliers, bank accounts, contracts and other records are marked on their own when the data is already in the system; the others show as "check it yourself".

The platform team now manages the verticals catalog through screens: the market tree with a preview of how an account would see it, modules by country, the requests accounts made with Request this, and publishing with who and when, with a way back to the previous version. Publishing requires being a catalog curator; Tenkai answers what accounts are requesting.

The UN international classification of activities, Brazil’s CNAE, the Harmonized System and the NCM are now loaded by Tenka straight from the official sources, with what changed since the last load, the rejected rows to download and the queue of correspondences to review. Each of the 87 international divisions becomes a vertical, so any company can find itself in the catalog.

When creating the account, the first step is to give the company’s country and tax ID: Tenka looks up the official activities, suggests the verticals for you to confirm and shows, before the plan, what already works in Tenka, what works by connecting to your system and what is coming soon in your country. Can’t find yours? Search by a word from your business or choose from the list.

Settings › Company has a new tab, Activities and verticals: the company’s country and tax ID, its official activities, its verticals per country of operation and which one is the main one. The Look up the tax ID again button brings the activities back in. The vertical suggests the package; what unlocks screens is still the plan and the profiles.

Tenkai answers whether your company’s operation runs on Tenka in your country: how much already works, what works by connecting to your system and what is coming soon, module by module, with the names in your language. You can ask about another vertical too, such as a bakery or a knitting mill.

Retail, grocery and bakery, distribution, importer, accounting firm, consulting and HR consulting are now in the choice of your vertical. Each vertical's implementation guide is now built from the steps of the modules your operation uses — starting with Settings and Finance — in the right order. Strategy, Processes and Tenkai got their own guide, and the addresses of the old playbooks still open.

When a screen does not open, the page says why: the group that grants it belongs to another company, you are not in a group in this company, the View permission is missing, the screen is not in your groups or the plan does not include the module. In User access, Why doesn’t it open? shows it company by company. And the group record now has Copy to another company.

In Access, Suggested groups builds the Finance, Sales, Operations, Purchasing and inventory, HR or Leadership group, shows beforehand the screens it will open and applies it to one, several or all companies. Operations already includes your vertical’s modules.

With the store PIX key in the POS settings, choosing PIX opens the QR code with the amount of the part: the customer points the camera and pays, you check the bank app and click PIX received. The part only enters the payment after that, and the QR code is valid for a few minutes — if the customer gives up, the sale stays open for another method.

In the POS settings, the card machine, PIX and the tax device (MFE or SAT) can run in training mode: the card is approved at once (amounts ending in 51 cents are declined, to practice declines), PIX gets the Simulate payment button and the tax receipt is built and checked without being sent. A banner warns that the register is in training, and in the environment with real sales training never turns on.

The Day queue now has “Resume what stopped”: the proposal you left as a draft, the quote that stayed open and the agent step waiting for your decision show up there, and the click opens it the way you left it.

With a BI dashboard open, write to Tenkai "show only the Centro store" or "clear the filters": it applies the filter on the dashboard itself, the numbers recalculate right away and the answer confirms what was applied. Questions like "which store sells the most?" are still answered about the numbers on screen. There is also the "Why did it drop?" suggestion, which explains a drop through the dashboard’s calculation trail.

The customer record has a Tenka score tab: the sentence on how they pay and the factors that weigh (punctuality, swings, how much revenue depends on them, margin), with each weight. The supplier record has an Exposure tab: how much you owe, their share of purchases, how you have paid and whether bank details changed.

Changed the category of a supplier bill? The change becomes a rule proposal in Curation (Tenkai context), ready to approve. Once approved, that supplier’s next bill is created with the right category and the screen says it came from the rule. Reconciler rejections also arrive ready.

In Company settings, Finance group, set the amount above which every payment needs approval, the categories that always need it, blocked suppliers and released ones. The payment file follows the policy and sends what needs it to Financial approvals. And an approved bill whose amount, supplier, due date or barcode changes goes back to approval.

With the company’s Asaas account connected and Pix charge created automatically switched on (Company settings, Finance), the daily routine issues Pix and boleto for receivables due in the next days. The bill record shows the QR and the copy-and-paste code, and the WhatsApp message carries the code. Payment settles the bill on its own.

In the IBS/CBS simulator, the Registered NCM × official table section lists items whose NCM does not exist, was withdrawn by a Gecex act or is not in the 8-digit format, with the amount sold in 30 days. The item record warns when its NCM is in that situation — before the invoice is rejected.

The Your operation in Tenka strip, on Home and in Explore data, shows your company's vertical, the country and the Already works in Tenka, Works by connecting to your system and Coming soon percentages. Each number opens the Map by vertical, with the same number module by module.

The MCP server screen shows the connector address and the steps for each store. Whoever connects signs in with their own Tenka login, no key: answers follow that person's profile, read only, and every call is logged. On the first connection, whoever administers the account approves the app in Connected apps.

Forward the bank slip or bill as a PDF or photo to the company inbox, writing "lança" (post) in the subject or body. Tenkai reads the document and replies with the fields it read and a code: reply CONFIRMAR with the code and the entry is saved under your approval limit. Without your confirmation, nothing goes in.

In the time records list, choose the AFD file from the certified clock and the punches come in by themselves: each person is found by CPF, a day that already has records is not overwritten and the month's hours are calculated as usual. A file with a gap in the sequence is rejected whole, with the reason, so no punch disappears unnoticed.

In the App Store, besides BI dashboards and agent designs, your integration recipe with your management system becomes a package other accounts can install. Password, token and keys never go along, and the installed connector starts switched off until the other account adds its own credentials.

In the collection plan, next to the target, you see the OTB committed (production orders for the collection products and purchase orders for its items) and the open balance. Over budget, the balance turns red. Without an OTB in the plan, the screen asks you to enter it. Ask Tenkai how much of the OTB has been used.

Load × capacity tells from when a new order that goes through the bottleneck can be promised: today plus the bottleneck queue days. In the production order, next to the due date, the same date appears; a due date before it is flagged.

Tenkai shows which status holds sales orders, incoming invoices and returns the longest, where they go back and what is redone, split by track version — so you can see whether the new rule helped.

On the project record, the Engineering tab connects the Git repository and measures time to merge, deploys per week and time to recover; tool and cloud licences now count towards the project's cost and margin.

In More settings, at the bottom of the record page gear, you create a tab with any name and move into it the fields you use together. It applies only to you, on that screen. Removing the tab sends the fields back to Data.

In the opportunity's Closing tab, the Reopen button sends the opportunity back to the pipeline, in the stage where it was. If it had generated a contract, the contract stays, and winning again uses the same one without creating another. The reopening is recorded in the history.

The Home page and the Help Center get a row of short videos with the first steps, and each screen's article shows its video. Captions in 11 languages, the transcript right below, and nothing plays on its own. When a screen changes, its video is taken down until it is recorded again. Videos appear as they are published.

Software houses, field services, consulting, trade and rental, retail, distribution, clinics, industry, law firms and households now each have their own demo account, with customers, items and six months of activity, and no empty screen in the journey. The same demo in every environment: what the video shows is what the customer clicks. In production the demo account is view only.

With A2A opened on the platform, each account decides whether to serve other agents, in Settings › Parameters › Integrations. The agent uses an API key of the account and sees only what the key owner sees. Queries come back right away; actions such as settling a bill are only proposed, and nothing is saved until the person authorizes and the agent confirms in the same task. Everything goes to the audit trail.

On an account that requires data residency, no call to the AI provider leaves for another region: chat, audio transcription and live voice are refused before sending, with the reason and how to change the provider. On the Accounts screen, if the required region is not the one of the installation database, a notice says the database stays where it is.

The super admin isolates an account with one click: Tenka creates the dedicated database, copies and checks the data table by table and moves the account with a few minutes of scheduled maintenance. A new account can be born isolated at registration. For 7 days the old copy is kept and Undo reverts the move; then it is deleted automatically, with a record.

One screen shows every database — the shared one and each dedicated database — with its accounts, space used, version, connection health, cost, what we charge and the margin. Tenka suggests isolating Enterprise accounts or those over the limits, warns in Vigilance when a database falls behind on an update and, in that case, shows scheduled maintenance to its accounts instead of a broken screen.

Whoever builds your company integration now tests in an environment separate from production: in Settings › API keys, generate a sandbox key and use it at the sandbox address, with demo data on the same version as production, recreated every week. The sandbox key does not open production and the production key does not enter the sandbox. Outside production, a strip at the top of the screen tells you which environment you are in.

Approval, request, finance, Tenkai Watch and followed-record alerts now follow your choice in My preferences › Notifications: right away, in one digest a day or muted, separately for the system, phone, email and WhatsApp — and they arrive in your language. The same screen shows what happened to each alert, so you know why one did not reach you.

The public status page gained the panel "What each plan promises × what we measured (90 days)": for Free, Start, Grow and Enterprise, the policy's availability and first-response deadline, what was measured in the last 90 days, and the verdict. A promise you can check, not one you have to believe.

On the Sector benchmark screen, accounts that take part in the comparison see, indicator by indicator, the median and quartiles of accounts in the same industry and which range their own account falls in — margin, collection period, average ticket and, in textiles, finishing loss. Nothing shows with fewer than 5 accounts, each account counts as one anonymous point and taking part is the account administrator's choice. The same comparison is available in BI and in Tenkai.

Anyone who wants to try Tenka asks for the demo with name and e-mail, confirms with a six-digit code and browses the showcase for seven days. The demo carries a watermark with the visitor's name and does not export lists.

Every Tenkai answer shows a confidence badge — high, medium or low — according to the proof behind it: a data query, a calculation or model text only. Thumbs down sends the answer to the account's curation.

In BI each metric has an owner, a written definition and a validity date. Tenkai answers with metrics that have this contract and says when it declined for lack of one. There is also incremental export to the customer's data warehouse.

The accountant's cockpit now has the month-end close checklist, recalculated daily, and revenue recognized by accrual from each contract's schedule.

Payments split into queues: low risk goes ahead, ambiguous asks for approval, suspected fraud is held. Paste the DDA slips to check them against accounts payable.

In the IBS/CBS simulator each NCM sold shows green, yellow or red against the official table, with the amount at risk; apply the suggested classification in bulk. The impact comes by NCM, customer and supplier.

With the batch carbon factor declared by the supplier, the passport shows a verified footprint. Publish the passports of a whole collection in one click; the CONMETRO label now carries the QR code.

Every save that changes a component becomes a version with what changed and the garment cost. A materials library with current cost and certification, and a link for the customer to approve the sample.

Production load shows the bottleneck among cells, looms and machines, adding the setup of each article change. Ask Tenkai which one is the bottleneck.

The work order suggests the technician by skill, distance, deadline and day load, and confirms the time with the customer through the company’s WhatsApp.

Adjustment by the Central Bank’s IPCA or IGP-M, interest, fine and fees with the month-by-month working, saved to the case history.

All the account’s events in one place, with filter and replay; each delivery carries the contract version and, on replay, the original id.

The /api/v1 no longer breaks (a breaking change goes to /v2), the JavaScript and Python SDK comes from the contract itself, and another AI agent can ask Tenkai for tasks over the A2A protocol once the platform turns it on.

BI dashboards and agent designs become signed, reviewed packages another account installs in one click; and the account can require AI to use only providers in its region.

The Help Center has two new implementation guides: one for grocery stores, bakeries, butchers and produce shops (scale labels, price upload to the scale, store credit with a limit and cash count at closing) and one for importers (import process with taxes calculated and the landed cost in stock).

A step-by-step integration guide and one page for each API operation, with every field, every error message and the ready-made call in cURL, JavaScript, Python, Java, C#, PHP and Node. And the Help Center search now finds the portal when you type developer, API, SDK or webhook.

In Settings > Integrations every card now has a Turn on button: pick the system (Sankhya, TOTVS RM, Slack, Teams, GitHub, GitLab, Zapier…) and fill in only what it requires — the recipe handles the rest. The technical screen stays under Configure, as advanced mode. Bling, Omie, Tiny, Conta Azul and Open Finance already show what they ask for, marked "queued" until their extractor lands.

An ERP connector, team channel, API key or MCP that is on but has had no event for more than 7 days (adjustable in Parameters) becomes the "Stalled integration" finding in Tenkai Surveillance. In the hub, the Test button checks the connection right away, using the same test as the source screen.

The new Today''s queue screen joins approvals you decide, Surveillance findings, requests you own, Tenkai proposals awaiting confirmation and "it is on you" deadlines. First what only you can solve, then overdue and nearest deadline. Approve and Resolve in one click. Ask Tenkai "what do I have to solve today?".

In the team channel, "/tenka ask how much is due this week?" answers with your own access and a link to check, through the same engine as WhatsApp and e-mail. Once, beforehand: "/tenka link your@e-mail" sends a code to your e-mail and "/tenka code 123456" confirms who you are. Text without the verb still opens a request.

In the financial transactions list, the "Post from document" button takes the photo of the bank slip or the invoice PDF, Tenkai builds the posting proposal (the same as WhatsApp and the chat) and you confirm with one click. Nothing is saved before Confirm. In expense receipts by photo, the category is now suggested from the merchant and the document number goes into the description.

Ask Tenkai "a sales dashboard by salesperson and by month": it proposes the total card, the trend over time, the ranking and the share, each with a preview, and the "Build the dashboard" link opens the builder with everything ready. Then adjust by talking: "switch to donut", "only the South region", "last 6 months" change the last proposed chart without repeating the question.

Every Tenkai answer now has a "Repeat every Monday" button: it opens the Agent Builder with the request ready and already interpreted — you check and publish. In the Builder, four role-based agents are ready to start: Financial Analyst, Production and Purchasing Planner, Anomaly Detector and Sales Assistant.

When the catalog watcher discovers a new model with a price, the evaluation battery runs on the current model and on the new one with the same cases. The Tenkai Evaluation screen shows accuracy, consistency and latency side by side, per model. Switching remains a human decision.

In the contract record, "Read the contract" takes the signed PDF and shows term, adjustment, penalty, renewal and venue next to what is saved — you apply what you want. A penalty or adjustment above the company's clause policy comes flagged. A contract with automatic renewal ending in 60 days becomes a Surveillance finding, before the notice period. Ask "what renews on its own?".

Each path item can have a quiz: learners answer and get a score; admins build the questions on the same screen. A finished path issues a certificate with a code. New hires are enrolled automatically in mandatory paths. The paths screen also shows the product paths and a report by area (progress, completed, overdue and average score).

The admin briefing now brings plan modules nobody opened in 30 days and lists the same person opens every day (candidates for a dashboard or an agent), with the Academy as the action. And ask Tenkai "where does the process stall?": it shows which stage holds requests the longest, where they go back to and where they are redone.

A component can point to a child dashboard: clicking a value opens the child already filtered by it. The whole dashboard goes out as JSON (components, filters and profiles by name) to take to another company, and comes in as a draft on the other side. Each filter chooses whether it remembers the last value per person.

With GitHub or GitLab connected, Tenkai answers lead time, deploys per week and recovery time for each repository. The project got a third-party licenses tab as cost. In production, ask "where did the work order overrun" to see stage by stage, and the ABC Curve got a "production cost" mode.

In the Transparency Center, each digital employee exports its record in the AI Act format: purpose, powers, current rules, the month's scoreboard with untouched rate, incidents and the autonomy policy. PDF for the customer, JSON for the auditor.

The new Tenka showcase screen shows each module with its screens, what your plan includes and what arrived in the last two versions — in your language. The numbers come from the system's own catalog, never from a hand-written list.

The POS got Till mode: the system menu and bar disappear, and the top strip shows operator, company, till number, clock and whether the station is online. Shortcuts F2 search, F3 quantity, F4 pay, F6 cash out, F8 remove item, F9 close till and Esc, with the legend at the bottom. Scan the code and press Enter: the item goes straight into the cart.

When closing the till, the operator types what was counted in cash, PIX, debit and credit without seeing the expected amount. The difference for each method only appears after confirming, and is recorded in the till trail.

In Chrome or Edge, the POS reads the scale weight straight into the quantity and opens the drawer through the non-fiscal printer — even automatically on every cash sale, if the station wants. The integrated card machine (TEF) arrives when the provider is chosen.

A sale can be paid in parts — cash, PIX, debit, credit in installments, voucher, cashback, customer credit and on account — until the total closes. In cash, the till types what was received and the change shows large, opening the drawer. One receivable per part.

Discount on the item or the total; above the company limit the POS asks for an authorizer's password and records who authorized. Removing an item asks for the reason and, above the per-till quota, also asks for authorization. Everything shows in the till reading.

F10 brings the picked order or quote into the cart and marks it invoiced. F7 puts the consumer tax ID on the receipt without registering a customer. F11 picks the salesperson, which commission now reads.

The "On account" method sells on credit to customers with a credit limit: the till sees limit, open and available, and installments are created as receivables. Above the limit it refuses, stating the numbers.

The receipt (and the NFC-e DANFE with QR) prints on the till printer over the serial port, even automatically on every sale. The X reading shows the open till per operator; at closing the Z reading is e-mailed and the notes-and-coins grid adds up the counted cash.

In Price lists, promotions gained a rule: buy 3 pay 2, price by quantity (wholesale) and discount by day and time. The POS applies it to the cart automatically and shows what it applied. Tenkai answers "which promotion is on".

Sale for delivery opens shipping with the address. F12 looks up price and stock in every company of the account and prints the item label. The scale label (EAN starting with 2) enters through Enter, and the scale load file exports the PLUs. In returns, the return invoice references the sale's NFC-e.

The public Help Center gained the Portals and access row (customer portal, pages that arrive by link, doors for other systems and how to install on the phone), the Integrations row with the whole catalog and the "Is everything up?" shortcut to the status page.

The public status page shows one bar per day for the last 90 days, the state of each component (application, database, job queue and those with open incidents) and the variation and peak of users and response time over the last 7 days — all measured by the platform itself.

The public status page says in its first line whether everything is operational, shows availability over 24 h, 7, 30 and 90 days, a 90-day bar per component, the updates of the last 7 days, scheduled maintenance and the history by month. Whoever wants to be notified leaves an e-mail and confirms by link; monitors read /status.json.

The Help Center gained the developer area: first steps with the key, authentication, limits and errors, API reference, webhook catalog, MCP/A2A/SCIM/SAML, SDK, change log, best practices, FAQ and status — in 10 languages.

GET /api/v1/<resource>/{id}/alteracoes returns who changed what and when in a customer, contract, bill or any API resource — the same trail the screen shows. Switched on and off per account in the parameter "API: change log per record".

In Settings › Map by vertical you see, one lane per area, every screen of your vertical linked by the path of your daily work — each box opens with one click. What your plan unlocks is coloured; what your account does not have yet is grey and visible, so you know it exists before you need it. The shortcuts switch the vertical to compare, and Tenkai answers "what does Tenka have for my area?" from the same map.

The support tables on the screens, such as the four in Profitability, now have their own gear next to the CSV download button: choose the columns, order, rows per page and density of each one. The CSV comes out as the table is on screen, and your choice is saved for you.

Below each answer, Tenkai says how many lookups it ran and how long the data took. Open it and each step shows what it checked, the criteria used, how many rows came back and a link to check it on the screen itself, with the same filter. The answer ends with a perspective line: what the number means and where to start.

Ask "why did the cost go up?" or "what explains the drop in sales?": Tenkai compares with the previous period, breaks down what weighed the most (by customer, product or category), opens the answer with the main cause and ends with "How to fix", saying the next step and the screen where to do it. Each lookup appears in the steps, with the link to check it.

The top became a single bar in your company color, with search in the center, the Ask Tenkai button, quick settings (language, visual mode, menu and interface size), notifications, help and your account. Right below are Back, the path and the screen name with the star to pin it. Tenkai opens as a panel on the right, and the thin footer shows your plan and what is new.

The Help Center now has the roadmap for the whole textile chain, from the cotton gin to the store, in a group of several companies, plus one roadmap per link: cotton gin, spinning, knitting, dyeing and finishing, apparel, sewing contractor and fashion store. Each step opens the system screen and its help, and the simulator suggests the plan with its cost.

Every list now has the download icon in the right corner, next to the view tabs: Excel or PDF of what is filtered (not just the page) and the full CSV of the base, which asks for your password. It is the same icon as the other tables in the system, which download the rows shown as CSV — now in your language.