Tenka Help Center › Release history
Release history
Everything that changed in the platform, release by release, with the full text of each item.
Period
Kind
When you remove a connector in Settings, Connectors, it no longer disappears for good: it goes to the trash and an Undo button appears. In the trash you can restore the connector or delete it permanently. A connector in the trash receives no notifications.
When you sign in to the portal with an e-mail that has no access, the "invalid e-mail or password" answer comes back right away instead of leaving the page loading for many seconds.
In the Contract summary PDF, the Outstanding amount adds up only the invoices still to be paid: a cancelled invoice no longer shows up as money owed. It is the same calculation used on the contract page.
The contract status shows as Active, Suspended, Closed and so on, in your language, on the contract page, the contract list and the Contract summary PDF, and no longer as an upper-case code.
The Projects in progress panel on the Home page lists every active project, including those with no deliveries planned yet. Before, Home could say "1 active project" and "No project in progress" at the same time.
Screen readers now announce the Ctrl+Enter shortcut to send and tell you when new messages from support arrive; icon tips also show when you move with the keyboard; and when your company color is light, the text on buttons and messages turns dark to stay readable.
In My preferences, on the Notifications tab, there is a new row, New message in Support, to choose how you get the notice when a customer writes in the portal chat, without silencing the other system notices.
An hour logged on the 31st and approved on the 2nd now counts in the month it was worked, everywhere: in Profitability, in the hour bank balance, in the overage and in the customer portal. Before, Profitability and the balance used the approval day, and the same work fell into different months.
In the Contract summary panel, the Hours column says how many project hours are still awaiting approval — they only use the bank once approved. In the Value column, when the portal total differs from the billed amount (an expense marked as visible to the customer, or revenue hidden from them), the summary shows the number the customer sees. In the Profitability tab, each month’s labor amount opens the list of hours behind that cost.
To record a shift with production, enter the yarn and the kilos of yarn consumed: the knitted fabric does not enter stock without the yarn it came from. A shift linked to a production order still does not ask (the order already issues the yarn). If the yarn has no cost, the fabric enters at zero cost and is flagged for the closing and the cost of sales. The Article and Yarn fields no longer list items in the trash, and items without an NCM code appear at the end of the list marked "no NCM".
When generating the export NF-e, the shipment rate is compared with the day’s quote registered in the exchange rates. If the difference exceeds 2%, the invoice warns with both numbers so you can check before sending. With no quote registered, the invoice is still generated, but it warns that the rate was not checked.
Each AI usage line now records the model that actually answered (for example, the dated version of the model, or the model the provider chose), not just the configured one. The cost and the margin per account now use that model’s price.
In the ticket’s Time entries tab, the trash button now asks before deleting and warns that, if the hours counted against the contract, that usage is removed too.
When viewing another account’s data, the disabled Save explains that it is a read-only view where nothing is saved. Before, it only said permission was missing.
Old opportunity history lines without a type showed "null: 1". Now they show only the change.
The path card could say "0 page(s)" on a path with lessons. The count now follows the path.
"Collect now" no longer checks one by one the accounts with nothing to check (no audit trail, or only shared profiles). The result is the same.
The "Value delivered report" PDF, downloaded from the portal Home, came out in Portuguese for every client. It now comes out in the client’s language, and a project with no deliveries planned yet says so instead of "0/0".
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 any list with import, when your file's header does not use the name the screen expects, the preview shows each field with the file column for you to choose. Apply and remember redoes the preview and keeps the choice for your company: the next file in the same layout comes in right.
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.
Completed phases, budget used, health, margin and hours at the top of the project record now come from the same calculation as the Project P&L tab: hours worked in work orders, tickets and the project, and the cost of who did them. Before, the top could show zero next to a full P&L.
A work order that came from Sankhya now shows its number there, with the source next to it ("Sankhya 91016"), in the list, the record, the P&L cost by phase and the project timeline. Search finds it by that number, and the list has a new Source column.
A work order in Service mode (a consultant’s work) no longer shows equipment, serial number, check-in, check-out, travel, report or the Schedule and field tab — and the list stops showing equipment and serial number when the account does no field service. Field work orders are unchanged.
In Ctrl+K, screens such as Customers, Roles and costs, Employees and the connectors showed up twice. Now each screen appears on one line.
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.
Went over the pack allowance? The contract summary now shows, month by month, the extra hours and whether they were already invoiced or are still to be billed. The amount shows for people who can see values; the hours, for everyone. It is the same figure your customer sees in the portal.
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.
For a services company, Live margin no longer opens with “no sales”. With no product sales in the last 12 months, it shows the portfolio of fixed-scope projects — revenue, hours cost and margin of each, using the same calculation as the project P&L tab.
Clicking a column title in Financial movements now really sorts the list — and the Excel, CSV and PDF exports come out in the same order as the screen. Without a click, the list stays by most recent due date.
On the screen that says you have no access, the Back button now returns to the page you came from (or Home). And Home and menu shortcuts to screens your profile can't open no longer appear, instead of leading to a refusal.
When you save a time entry on a request, billable hours are now the hours worked times the multiplier you typed: 30 hours with multiplier 1 bills 30, even if the start-to-end span is 24. And “Outside hours” no longer ticks itself. Negative values are refused. Calendar, timer, phone and API keep classifying by the calendar and the contract.
Text, type, owner, project, sprint, customer, workflow, “only mine” and “only open”: the filter you applied comes back when you refresh, leave and return, or sign in from another browser. Clear resets what was saved.
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.
In Users and access groups, pressing Enter in the new-user fields registers the user. The “Link to group…” field only shows when the company has a group to choose; if not, a hint takes its place. The search magnifier no longer covers the text and the fields are aligned.
In Tenant settings, the account administrator can again create an affiliated company and save the company data without getting the permission request. People who are not administrators, and read-only visits, stay blocked.
In a contract price, Quantity accepts up to three decimal places — 2.5 hours, 0.125 kg, 1.333 units — and the Qty column shows the number as typed, with no extra zeros.
The footer total of lists no longer shows as money on quantity, weight and energy columns: Contamination showed “R$ 16,500.00” where it was 16,500. A currency column keeps the currency symbol and stays under “Show values”.
When customer acceptance is on, the project P&L and the Live margin project portfolio show how many work-order and request hours are still awaiting acceptance: their cost is already counted, but the contract’s hour bank is only consumed after the customer accepts.
When the project doesn’t show the consultant to the customer, the list of hours awaiting acceptance in the portal now shows the role of who did the work (the job title) instead of the name. With the consultant visible, the name still appears.
On a purchase invoice paid with the partner’s card, the Payment block now brings the cost center of the last reimbursement posted. You can change it or leave it without a cost center, as before.
At the checkout, Shift+F8 discards the whole cart asking for the reason, and the register stays open; above the cancellation quota it asks for approval from someone with authority. F6 switches between cash withdrawal and top-up. In the cash count, "460.10" is the same as "460,10".
When you save the loom shift, the yarn consumed leaves stock and the fabric produced comes in. If the production order already makes that movement, enter its number and the screen does not count it twice. Without yarn balance nothing moves and you see why.
The yarn and article lists in Loom production and Yarn consumption per article now also show covered yarn, velvet and pile fabric, and coated fabric.
Whoever confirms an import leaves a record in the audit trail: who, when, how many rows and from which file. The import preview now scrolls sideways and the columns stay readable.
When you delete, the Undo bar says the screen name in your language (for example, "Treasury contracts (1) moved to the trash") instead of a technical name. The tip for the "Requires Legal approval" field also shows in your language.
The customer record opens faster: the Relationship, Vouchers and benefits, Tenka Score and Group tabs load when you click them. The stock movements list also opens faster in companies with many items.
In the Charges by regime record, previous and next move only through the charges the list shows, and the count matches it. In the timeline, a record without a date shows "on —".
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.
Recalculating contract hours is now all or nothing: if one request cannot be redone, nothing changes and the screen says which one to check. Deleting a time entry removes its hours from the contract at once, without leaving the contract short of hours if something goes wrong.
The status color from the registry stays readable in light and dark themes, in the contract Requests tab and in the requests list. Every change to the git connector settings goes into the audit trail with who and when; the token never appears in the record.
The seller portal has a Copy link button, billing and lead status in your language, and empty lists that say what to do. Asked Tenkai how much commission you will earn as a partner? It answers from your portfolio.
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 record, the Request owner, Automatic renewal, Notice period and After-hours multiplier went back to the previous value when the contract already existed. Now what you choose is saved when you save.
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 portal Home, a contract split between the head office and a branch showed twice under Active contracts. Now each contract shows once, and contracts in the trash do not show.
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.
List searches are no longer filled in or filtered by your login email. In the contract cockpit, Margin by contract and the Contract Health Score sit side by side. When adding a pack to the contract of a client with no linked product, the list shows the company catalog and says so.
In the request record, the steps bar only lets you click the step the type's workflow allows from the current status; the others are greyed out with an explanation. Changing the status from the record, from Move activity in the list or by bulk edit follows the same workflow, estimate, solution and automation rules, and the history gets a single line.
The trash opens without errors on the screens that used to fail. When a record goes to the trash, the system keeps who deleted it and shows it in the "Deleted by" column. Restore and Undo keep working. Records already in the trash before this version show "Deleted by" blank.
Checkout sales close faster: stock for the items is written off in one go for the whole sale, and an already paid Pix is checked in a single pass. Item balance and cost stay the same.
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.
The contract hours chart, on the record and in the portal, now has an hours axis, a bar with each month's consumption and the name of each line at its end: planned balance, actual balance and balance trend. On top are the total contracted, used to date, today's balance and the end balance by trend.
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 Tickets on the portal, Download builds the report with the same tickets the list shows, with the same filters and period. With All periods, the report starts at the oldest ticket. Before, it brought only the current month’s support tickets.
Approved hours on the projects linked to a contract now use the hour bank, like ticket hours. They count in the balance and in the month-by-month chart and, above the cycle limit, become overage. A pending hour is only used once approved, and a rejected hour is not used. On the contract record, the new Projects tab shows each project with approved hours, pending hours, what went into the bank and the overage. On the portal, the contract page lists the projects with their approved hours. Each hour counts only once: a ticket that belongs to a project still counts as a ticket.
The customer portal now uses your company’s registered colors, the same as the system: buttons, links, tabs, the current page of lists and highlights. With no color registered, the portal keeps the default colors. The color is changed in the company record and applies to both.
On the contract Overview, one panel shows the contract in three columns, always in the same order: contracted, used and balance. Value shows the contracted amount for the term, what was already billed and what is still to bill. Hours shows contracted hours, used hours (tickets and projects) and the balance, with the trend. Profitability shows billed, cost and margin. The contracted value comes from the contract products and prices; without them, from the monthly value on the Data tab. If both are filled in and differ, the panel says which one applies.
A completed request delivered before the forecast date saves again. The warning now only shows if delivery is before the request was opened. A new request of a type without a workflow starts in the first active status, and changing status from the list column follows the workflow.
Hours logged on requests without a project, such as contract support, now count in the customer's labor cost in Profitability on the day they are approved.
When you restore a loom production from the trash, the yarn leaves stock and the fabric comes in again, just like on save.
The shipping manifest saves again: Status, which is locked on screen, starts as Open and no longer shows up as an empty required field.
A new request saves without the false error. In Comex, "New item" opens the form and the export invoice can be created. The bell shows notices that arrive while the screen is open. The phone register closes in seconds. The Status pencil on the request list shows statuses by name. The Studio asks for confirmation before removing an attachment.
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.
Enter the third party's invoice key or import its XML. The system checks the key, the CNPJ and the CFOPs and warns when an invoice is missing or something doesn't match.
In search (Ctrl+K) and in Tenkai, typing "grid", "sizing", "pack" or "size and color" takes you straight to Received shipments, where each line of a shipment by size grid shows the piece's size and color. Before, the screen was only found by the shipment name.
The piece name with its grid — "T-shirt — M / Blue" — is now written the same way at the register, in exchanges and returns, and in Received shipments. A piece that only has a size (or only a color) shows as "T-shirt — M", with no stray dash or slash.
When closing the register on the web, the "Bills and coins" block had a light background and an almost invisible title in the dark theme. Now the background, the title and the fields follow the theme and are readable in both light and dark.
On the Status classification form, the Key field is now called Code. Tenkai answers about classifications by name only, without the code, and search also finds the screen by request classification. The requests Kanban help explains that the sections come from the classifications.
A contract from another customer no longer gets into the ticket, whether through the record, Tenkai or an integration: the message says which field to change. The record also warns when the contract list shows only the 2,000 most recent ones and says when to save to see the new customer’s links.
Like the Z report, the X report now shows the amount and count of each payment method, for example Pix R$ 49.90 (1). And the opening screen tells you when the register was already closed today on this phone.
Removing an already-paid Pix part now responds right away: the part leaves the sale, the charge is set to be refunded and the notice reaches the bell of whoever checks the register right after.
Dragging the card on the Kanban, completing or reopening in My Agenda, starting or pausing the timer, pausing or resuming from the row menu and changing the status through the integration follow the same rules as the record: the type workflow, the estimate, the written solution and the stage done checklist (before, only the Kanban checked the checklist). "On status change" automations now run on every change, and only they do.
Deleting a time entry whose hours are already counted in the contract usage now requires the delete permission in Contracts; without it, the screen tells you why and nothing is deleted. Hours already invoiced still cannot be deleted.
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.
The leads, sales and invoices lists in the partner portal show the most recent ones and, when there are more, say "Showing N of M". Asking Tenkai about the commission receivable gives the same figure as the portal card.
On any screen, hovering over a button disabled because your profile can only view shows the reason: "Read only: your profile can only view this screen. Ask the account administrator for permission to edit." Before, this only appeared in lists, standard records and finance.
When a commit or a merge moves the request and the git author is not a user of the account, the history and the comment are recorded as "Tenka (automatic routine)", no longer as the company owner. The same GitHub or GitLab delivery sent again does not repeat the comment, the hours or the move.
The "1–25 of 3,458" and the rows-per-page choice are back at the bottom of every table. You can see at a glance how many open demands, customers or bills there are.
Open, Overdue, No owner and the other cards now count only what the list shows: the view, filters and search. Before, they counted the whole company even with a sprint filtered.
Opened a record from a filtered list? The "n of N", previous and next now go through that list only, in the same order — not the whole table. It works on every record page.
Find grows to fill the space and Save is always at the end of the line. When you open or close the activity panel, tabs that do not fit go to "More" instead of being cut.
Typing "Demand" in search (Ctrl+K) brings the Demands list first. Before, it disappeared: the "New demand" action hid the screen. A screen whose name starts with what you typed now comes ahead of similar ones.
When the configured AI model is down or the key is rejected, Tenkai now says so and where to fix it (Settings › AI), instead of "try again in a moment". While analysing, the button itself shows "Analysing the numbers..." without pushing the others.
The "Notifications" title and "Mark all as read" are clear on the header, like quick settings. When viewing another company in view mode, a refused save says "View mode" with the reason, instead of "Internal error".
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.
The next 14 days appear as cards labelled by type (market, extra shift, excursion). The form only opens with "Add a market day" or Edit, already filled in. The table below now has a title: the reseller buses.
Shops and lives, photo on a model, Tenkai listing and exchanges are now separate numbered cards, each with a "what it is for" line and an example. The shop form only opens with New shop, New live or Edit.
With a logo, the brand sits in the centre of the menu band; without one, the initial sits in a square tile, centred.
The "Assigned employee" column (who does the work) can be turned on in the Demands and Tickets lists, right after "Owner". It starts off: turn it on in Column preferences.
A table used by several screens opened through the last screen read, sometimes with no fields — so you could not mark Demand fields as "Required". Now each table opens through the screen with the full dictionary.
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.
"Build route" is the main button and "Refresh" is now secondary; the day’s manifest cards are no longer stuck together.
The Demand description field can be stretched by its corner again, to write and read long texts.
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.
Opening and saving a request erased the contract, package, contract item, environment, product and project delivery it had. These fields now stay as they were, and logged hours keep counting toward the right contract. If one of your requests ended up without a contract, choose the contract again on the record and save.
In the requests list, the Trash item in the menu did not open anything. It now shows deleted requests, with who deleted them and when, and from there you restore or delete for good.
In the requests list, the Status column gets a soft background in the color chosen in the status setup, so you can spot at a glance what is in each stage. Statuses without a color stay as before.
When relating one request to another, the choice list showed a number different from the code in the list’s Code column and in the search. It now shows the same code, also in the Relationships tab, and you can search for the request by it.
Anyone with a timer running on a request that went to the trash got an error page when opening Tenka. Now, when the request goes to the trash, its timer stops right away with the hours recorded up to then, and the home screen opens normally.
In financial entries, the projected cash flow chart now takes the full width of the screen, with each month's inflows, outflows and balance easy to read. The accrual filter now has "from" and "to": pick both to see several months at once, or leave "to" blank to see a single month.
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.
When the garment maker sent a shipment by size grid, the sewing shop saw in Received shipments several identical lines with the same piece name and could not tell which size or color it was returning. Now each line shows the size and color, for example "Ribbed blouse — L / BLACK", in the list and when returning.
When a request goes to the trash with someone’s timer running, the timer stops right away with the hours recorded up to then, and that person gets a notice saying which request it was and how many hours were kept. Whoever sent it to the trash does not get the notice.
Editing the hours of a time entry counted the same hours twice on the contract, and deleting a time entry gave an error. Now the hours deducted from the contract follow edits and deletions. In the contract’s Requests tab, the Recalculate contract hours button fixes what was already wrong; what was already billed does not change.
The Logged hours card in the contract’s Profitability now shows all hours worked on the contract, the same as the Requests tab. Right below it shows how many of them count toward cost: only approved ones, with a team member and a start time.
When the project has delivered its part and is waiting for the client, use Wait for the client in the record’s menu and say what you are waiting for. Meanwhile, an overdue forecast does not count as a team delay: the project moves to the Waiting for the client column on the board, the PMO panel shows the client wait apart from delays, and the record shows since when. Use Resume the project when the client replies.
If you left a screen open for a few minutes, reading the demand list for example, you could suddenly land on the Just confirming it is you page. The automatic refresh of the notifications bell was mistaken for robot browsing. Now only moving to another screen counts, and the confirmation appears only for real automated browsing.
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.
The contract Requests tab shows the request code as in the requests list, the status in the same color, the owner and the sprint. The contract balance appears next to the hour totals, and zero hours show as a dash.
Analyze contract with Tenkai moved to the title line, as on Home. Actions are now in two groups, Renewal and Price adjustment, with Cancel contract set apart. The No invoices, Overdue and Signature pending notices now show only when they apply to the contract.
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.
Requests the client opens through the portal or by email now arrive with their active contract, consuming the contract, with that contract's request owner, the product (when the contract has only one) and the sprint in progress. If the client has more than one active contract, the portal asks which one the request belongs to. Whatever cannot be filled in still goes to "Classify and Assign Fields". What the client calls a ticket appears to you as a request.
In the contract overview, the "Request owner" field says who handles that contract's requests. That person appears as the responsible employee on requests the client opens, and the request goes straight to their schedule.
Request automations now have a "Client" filter and an "Assign to employee" action, and they also apply to requests coming in through the portal and by email. Use them for exceptions: a client whose requests always go to someone else.
After you close the register on the phone, it no longer reopens on its own the same day: the day ends closed and tomorrow's float goes in when you open. The Z report shows each payment method with its name and amount in currency (Cash R$ 49.90).
In the POS, the list that appears when you search for an item now shows the store price list price, the same one that goes into the cart and the same as on the phone register. Before, the list showed the catalog price and the cart charged another. At closing, the cursor starts on the first banknote, so you can count with the keyboard only.
In lists, right-clicking anywhere on a record opens the same menu as the row's three dots (Favorite, View, Edit, Duplicate, Open in new tab and Send to trash), right where the cursor is. Over a link or with Ctrl held down, the browser's menu still appears. The menu shows only the options you are allowed to use.
When confirming a demand import from the spreadsheet, the rows were saved but the page ended on "Oops! Something didn't go as expected" and you had to go back to see the result. Now the confirmation ends on the list itself, with the message of how many demands came in.
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.
With the option "Confirmed order creates work orders for what is missing" on, the production order for what the size grid lacks is also created when the order is confirmed by the payment link or when a quote from the catalog is confirmed — not only by the Confirm button. The order comes with the spec sheet routing, the missing grid and the priority from the promised date, and is never created twice for the same line.
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.
Counter plan users see only Items, Sell, Who owes me, How much I sold and Online orders in the menu, search and Home. The rest of Tenka is still there, one tap away in "See everything". First use is now three steps: add the item, see who owes you and how much you sold.
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.
With your Pix key set, the checkout (computer and phone) shows the QR and copy-paste code with the exact sale amount; the customer pays in her banking app and you tap "Received". It is the default for those starting out: no gateway contract, money goes straight to your account.
On the item grid, the counter label prints your price, the suggested resale price for the buyer (your price plus the house margin you set) and a QR the phone checkout reads with the camera.
For items you buy ready and resell, the price screen has a "Bought for, selling for" mode: enter what you paid and what you charge, and see what is left on each item, the price that gives the margin you want and how many items a month pay your fixed costs. Taxes come from your tax regime (zero for MEI).
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.
The pricing page and the Try page now have a version for stalls and small apparel makers, with no system jargon: the plans with the price that goes on the invoice and a call to start with your phone.
First use for apparel makers now starts with orders and shipping, then goes to the item, the tech sheet and production: newcomers sell before they design.
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.
When you asked Tenkai which models the account uses, the line saying where the answer comes from quoted internal system names. Now it says, in your language, that the answer comes from the models enabled for the account and the model catalog.
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.
Records and screens of spinning, knitting, dyeing, household finance, sales, supplies and LGPD got the question they answer and everyday names (for example "packing list", "barré", "card bill", "price per piece"). Now quick search (Ctrl+K) and Tenkai find them by the word you use, not only by the screen's official name.
The credit card, card bill, investment and recurrence rule records got help: what they are for, what each field means, how expenses reach the card and how the bill becomes paid, how earnings are calculated and why generating the recurrence twice does not duplicate anything.
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.
If the phone checkout was closed or reopened while the sale was still saving, the cart came back with the Pix already paid, as if the sale were open. Now the cart starts empty and the checkout tells you: the sale was already saved, or it is in the device queue and uploads by itself — it is never charged twice.
For people who use the stall menu and turned on "See everything", the side menu shortcut "Only the essentials of my line" opened a full management menu. Now it does the same as "See the essentials" in your user menu: it goes back to the stall menu.
The public pricing page had advertised the 1,000-credit Tenkai pack for millions of reais: sample usage from demonstration accounts was counted in the average cost. Now only real usage counts, and the price on the pricing page, My subscription and the credit purchase is the same and correct.
The top of an open work order showed an actual cost of 0.00 even with pieces reported — the cost only appeared in the Cost by stage tab. It now shows the actual cost accumulated so far and the cost per piece already reported; once the order is completed, it goes back to the closed actual cost. On the spec sheet, next to the actual cost of the last completed order, the order in production appears with its actual cost so far per piece.
Typing a work order number in the search — or opening the list from a link with the number — left the list empty when the number did not appear in another field. Now the record number is always searched, as an exact match: 1236 finds 1236, and 12 does not bring 1236. This applies to every list.
In the work order report list, what the seamstress reported by scanning the label showed as made on screen. Now the source says Scan, and a price adjustment proposal without a source order no longer shows "null" in its sentence.
When the warehouse chosen for the checkout had been removed from the records, saving any other setting saved the checkout warehouse as blank. Now the box shows the saved value and it only changes if you pick another one.
In an account with a single company, questions like "which automations are running?", "which records did I create?" and "what is the team doing today?" answered that there was no company or team, and the receivables forecast and the international-standard statement failed. Now Tenkai answers with what is in your account. It also refuses right away any request for a password, token or access key and for lists of people's documents or bank details, in any channel.
When a question could be answered by more than one query ("which teams do we have", "who did I spend the most with on purchases", "how much was in the central warehouse"), Tenkai sometimes picked the wrong one or said it didn't have the information. Now it considers only the queries related to the question and decides between similar ones before answering — and the answer arrives faster.
Questions like "which contracts expire in the next 90 days?" and "which renewals do I need to handle before month end?" answered that there was no data, even with contracts on file. Now Tenkai lists the contracts ending in the period, those that renew automatically and the last day to give notice. It also better understands "overdue tax slip", "what if my customers pay 15 days later" and "what is worth automating".
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.
Scan, tap Charge and tap the method: the sale is saved. Cash no longer asks for a change screen — if you want the change, tap the note you received or type the amount on the same sheet. The method of the last sale appears first and highlighted; splitting the payment and installments are under "Split the payment or pay in installments".
Tap the item name in the cart to change the quantity, the price or remove it. For a registered item, a price below the store price becomes a discount and, above the limit, someone with approval rights releases it on the same sheet — the sale does not restart.
The first sale of the day no longer stops at "Open the register": it opens by itself with the drawer at zero (drawer change goes in Menu, Cash in; stores that count the drawer at opening turn this off in Parameters, POS). And the camera now reads barcodes on iPhone too, with the same continuous beep.
Scanning an item in the phone register is much faster: the register remembers the store's price rules for a minute and reads the cart at once. Creating an account by phone is also lighter: what you need to sell (the Counter stock location and the register) is ready right away, and the rest of the account setup finishes on its own within seconds.
Before, when a registered item had no NCM or CFOP, the register's invoice went out with a guessed default code that the tax authority could reject. Now the sale is saved normally and the invoice stays pending, saying which item and what is missing in its record. Once filled in, the invoice goes out on the next attempt.
When someone changes their password, is deactivated or has the password reset, the register phones linked to that person are signed out at once and ask to sign in again. The phone opened from the Sell button signs out too when the person leaves the system in that browser. Demo visits and read-only access do not open the register.
Say or write the sale the way you do at the stall: "sold 5 size runs of the ribbed top", "5 pieces size M of the ribbed top to a walk-in customer, list price plus 5% on the card in 3 installments". The size run comes from the item record, with the right sizes; the price list can be named; the surcharge or discount and the installments go in as at the checkout. Before saving, Tenka shows each item with price, total and terms, and waits for your CONFIRM. Anything unclear becomes a question. When it asks, just reply with what was missing ("M red", "by Pix").
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.
An item sold by price alone in the phone register now goes on the invoice with the NCM, CFOP and CSOSN you set once in Company settings, Parameters, PDV ("Unregistered item invoice"), and with the description you wrote at the sale ("ribbed blouse"). Until that default is filled in, the sale is saved as usual and the invoice stays pending, saying exactly what is missing — it never goes out with a made-up code. Once filled in, the invoice goes out on the next attempt.
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.
If you are already in Tenka and tap Sell, you go straight into the register without typing anything. And if you created the account with just your phone, with no e-mail, you enter the register with your phone and the code that arrives on WhatsApp. E-mail and password still work.
Accounts created on the Get started page came without a stock location, and the first sale stopped with "the company does not have a warehouse yet". Now every new account starts with the Counter warehouse, already linked to the register, and Counter plan accounts that were left without it have received it too.
Creating the account on the Get started page waits less, and whoever uses the counter on the phone always lands on the counter Home, never on the time clock and payslip screen.
If the phone checkout was closed right as you tapped "Pix received", the Pix stayed paid with no sale and the cart came back without it. Now the sale goes in by itself with the paid Pix; when you open the checkout again it shows the sale number (or puts the Pix part back in the cart to finish). If the sale cannot go in, whoever runs the checkout gets a notice saying what to do.
At the phone checkout, unregistered items above R$ 2,000 in the sale (change it in Parameters, "Unregistered item: maximum value without approval") ask for the e-mail and password of someone with approval rights, like a discount above the limit — an extra zero no longer becomes a sale worth thousands. The approval sheet also gained a Reason field: the sale keeps what was written, or "Approval at the checkout" when nobody wrote anything.
Three sales made at the same instant could go over the monthly sales limit of the free plan; now they are counted one at a time. The "Unregistered item" the checkout creates by itself no longer counts among the plan's registered items. And the "ready by…" date no longer shows on the unregistered item, which has no production.
The order's Stock card showed the warehouse balance without subtracting what other orders had already reserved, while the production order created on confirmation counted differently: the order said "15 missing" and the production order opened 24. Now both count the same way — the shipping warehouse balance minus other orders' reservations — and the card says so.
The subcontractor lead time and quality table in subcontracting looked at the last 90 days, while the date promised to the customer and the workshop seal looked at 180 — the same subcontractor showed different numbers. Now everything uses the same 180 days, and the table title states the period.
The production order only showed the standard cost after it was finished — while open, it showed 0.00. Now it is created with the standard cost from the technical sheet. In the cost by stage, the column that divided the accumulated cost by that stage's pieces (showing a per-piece value much higher than the header) became "Accumulated per piece": the accumulated cost divided by the pieces already reported on the order, like the header. The production order and subcontractor shipment screens also open faster.
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.
The commission rule now has a product: subscription in the first year, recurring subscription, credit and add-on, each with its own percentage, always on what the customer paid. The advance agreed with the representative becomes a bill to pay right away and is deducted at the next closings until it reaches zero. An invoice cancelled after payment comes back as a reversal the next month.
In Users and access groups, every screen you add to a group shows up in its permission list, ready to allow add, edit and delete or to remove from the group. Before, screens that are not in the menu, such as the Partner portal, vanished once added and opened read-only.
People allowed to see amounts got "the amounts are masked" on WhatsApp for questions like "how much overdue do I have to receive" and "who sold the most". Now the conversation follows the same permission as the screen: whoever sees amounts in the system sees them in the answer; whoever does not keeps getting them hidden.
The customer record in simple mode now has a Delivery address tab: ZIP code (optional, fills in the rest), street, number, district, city and state, with no tax fields. It is the address tomorrow's delivery uses — and when the street is missing, the WhatsApp sale warning brings a direct link to this tab.
People who already had an account on the number and entered through the Get started page with the phone code sometimes landed on "Access denied". Now, after the code, the person signs in and goes to their own Home — the counter one, for those who sell at the counter.
In the production by machine record, the Article field now lists only knitted fabrics, with no yarns mixed in, and the Yarn consumed field lists only yarns. The split is by the item's NCM code; an item without an NCM code yet shows in both until it is classified.
When Pix billing is not yet turned on for the account, buying a WhatsApp or Tenkai credit pack only shows the notice and no longer creates a pending invoice that would fall due without anyone asking for it.
With no AI assistant turned on, asking in English which webhooks failed now brings the answer, and what was looked up, the follow-up suggestions and the EBITDA in the results show in the language of whoever asked.
In the owner cockpit, the menu of each open invoice now has "Cancel invoice". The reason is required and is recorded with who cancelled and when. If the invoice already has a charge in Asaas, the charge is cancelled there too; a paid invoice cannot be cancelled. The cancelled invoice leaves the open invoices, the collection schedule and the overdue account block.
Tenkai, WhatsApp and digital worker credits are paid before use: if the purchase was not paid, the credits simply do not come in. The invoice of that purchase does not become overdue in the collection schedule and does not block access for non-payment, not even when the charge was never issued.
Sending a loom production or a dyeing batch to the recycle bin, from the list, in bulk or with Undo, returns to stock the loss that had been written off; restoring writes it off again. And if the loss cannot leave stock, the screen explains why in plain words.
With no AI assistant turned on, questions such as cash balance, the month's result, receivables and payables, overdue customers, contracts about to expire, the month's sales and stock asked in English or Spanish now get an answer, with the period and scope in the asker's language.
If your session expired, your account has no linked company, your password change expired, or the SSO or passkey sign-in did not finish, the sign-in screen now shows the reason instead of coming back blank.
On the privacy page, the words “in force since” no longer run into the date of the terms and the policy.
On the sewing contractors’ plan, load, free capacity and “with this one” now show whole pieces. Before, 80 pieces of free capacity could show as “−80,000”, as if they were eighty thousand; now the plan says “−80”, the number you count on the floor.
On the knitting production list, search now also matches the article name and the machine name. Before, searching “Ribana” or “Tear 04” returned no rows even though they were on the list; now they show up. It works for the search box and for links that open with the term already filled in.
When you ask Tenkai for the month’s result with every company of the group selected in the header, the answer now adds up the whole group. Before, it repeated the numbers of the open company under the consolidated label. Each line’s percentage is now also calculated on the revenue of the same months it quotes: a negative EBITDA larger than revenue shows as about −114%, no longer as 7%.
When buying a credit pack on an account without Pix billing turned on, the notice “Pix billing is not turned on for this account yet” showed up twice at once. Now it shows once, on every screen.
In the contractors’ capacity screen, the “Contractor” field also listed tax bodies such as withheld social security, City Hall and the Federal Revenue. It now shows only contractors: those registered as such, those that already received a shipment or already have capacity saved.
On the stock panel, the turnover table, the below-minimum table and the digital buyer’s suggestions now show quantities the same way as the balance table. Before, 945.92 kg could show as “945,920”, as if it were almost a million; now it shows “945.92”.
When an in-house finishing pass is done on a customer’s material, such as raw knit fabric from a third party, the declared loss does not come out of your stock, because the material is not yours. Before, the form saved without a word and the loss looked forgotten; now a notice explains that the material belongs to the customer and that the loss stays only declared.
Opening a loom shift, or starting a new one, is now faster: the record no longer prepares the whole production list behind the scenes, which it does not even show. Fields, rolls and previous/next stay the same, following the same search you made in the list.
In the month-end closing in kilos, the salt, soda ash, dyes and auxiliaries weighed for the dyeing and washing baths now count as consumption of supplies. Before, they counted as material consumed with no output, and the knitting mill or the dye house ended the month hundreds of kilos short with nothing actually missing. In weaving, yarn already warped that is still on the warp beam waiting for the loom shows on its own line, “on the warp beam, not yet woven”, and no longer counts as missing kilos.
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.
On the Charges by Regime record, the header again shows which record you are on (for example, 2 of 5) and the arrows to go to the previous and next one without going back to the list. Before, the record showed neither.
In the phone app, buttons, links, checkboxes and options have a larger touch area, so your finger hits them the first time, without changing how the screen looks. And the Get to know this screen shortcut hides while it is over a field, coming back when there is free space.
In the production by machine record, the Article field also listed woven fabrics, such as linen and plain viscose, among the knitted ones. It now lists only knitted fabrics; an item with no NCM yet still shows up until it is classified.
When you open a contract link while “Viewing data from” is set to another company, the screen now says which company the contract belongs to and where to switch, instead of opening the “New contract — which type?” window over a blank form. If you have no access to that company, it only says the contract was not found.
Without AI turned on, asking Tenkai “what if my customers pay 30 days late?” fell into the list of overdue customers, and in Portuguese it came back asking “how many days” even with the number in the question. Now Tenkai reads the days from the question itself (“30 days”, “30 dias”, “30 días”) and shows how much cash gets tied up, the new cycle and the runway. “Earlier” or “faster” means paying in advance. Without a number, it still asks how many days.
When the company brings in more cash than it spends, Tenkai’s runway answer said “not burning cash” and, right below, “Average burn: −R$14,437.02”, while the card showed the same value without the sign, as if it were spending. Now it says “Average cash generation: R$14,437.02”, what is left over each month, in the reader’s language.
In the dyehouse, the loss declared on an approved in-house batch is taken out of the article's stock as soon as you save the batch — and comes back if the batch is reopened, deleted or has its loss corrected. The monthly closing in kilograms now only checks: it shows the loss that left stock and, separately, the declared loss that has not left yet. A batch that records dyeing done by a third party is not written off again: its loss is already in the shipment.
In the monthly closing in kilograms, the garment maker showed everything it cut as missing kilos (−100%), because a garment is not counted in kilos. Now the kilo that became a garment counts as produced — the usable weight the cutting weighed, or the production order write-off by the technical sheet — and the scrap weighed at cutting counts as waste. The unexplained difference shows only what nobody weighed or declared.
When one group company sells to another (the customer has the tax ID of a company in your account), the order goes out at the price agreed between them: the loyalty club discount no longer applies. Before, the knitting mill, the spinning mill's biggest buyer, got the club discount on yarn, and the group chain panel flagged as below cost a sale made above it.
In super admin, under Accounts › Create textile demo group, the Recreate from scratch button erases the operations of the eight Demo Group companies and rebuilds everything as the first time: the spinning mill again yields less than 100% of the lint, each company's margin stays within its industry range and no stock goes negative. Logins and passwords stay. Create or update still only completes what is missing.
If your profile changes in the middle of a sale, you can still undo the card or Pix payment the customer already made, and the register closes without a surplus. A Pix that had already arrived and is removed from the sale becomes an "amount to refund" in the bell of whoever checks the register. Each such undo is recorded with the register and the amount.
When a sale is saved but the item does not leave stock (stock month closed, inactive variant, a momentary failure), the sale is marked "stock to deduct" with the items and the reason, and it shows up in your queue for the day. In Till sales, fix the cause and tap "Deduct stock now": only what is missing leaves stock.
When the internet drops and the invoice is issued in contingency, an item without the tax situation (CST) in its record — under the Normal regime — keeps the invoice from being issued, and the till now says which item and what to fill in, instead of only warning that the invoice model did not arrive. Under the Simples regime, an item without CSOSN keeps the usual default.
A credit sale in 3 instalments now creates three receivables, one per instalment, each due when the acquirer deposits it (the credit term for the first and 30 more days for each following one), already net of the contracted fee. In the acquirer statement, each instalment matches its own receivable. Cancelling the sale cancels all instalments.
When the scanned item is set aside for another order and none is free in the store, the till asks for the e-mail and password of someone with authority before adding it to the sale — even when the person at the till has authority. Who authorised is recorded on the sale and on the order that lost the item. It applies to the store till and the phone till.
The Demo Group companies come with the profiles "Prova — Caixa só inclui" (till can only add) and "Prova — Caixa altera sem excluir" (till edits without deleting). In the Profiles list, pick one and use "View as": the till shows what that profile can do — a profile that only adds cannot open the till (operating needs the full profile) and one that edits without deleting sees no Delete button in customers. Nobody logs in with these profiles.
The name, CPF or CNPJ and network address of whoever accepted a proposal are kept as proof of the contract until 5 years after it ends. After that, a monthly routine erases them without waiting for the data subject’s request and records it on the proposal; the acceptance date stays.
The Digital employees’ office has a new "Runs this month" card: how many runs the agents have done against the plan’s allowance, the package balance and how many go to the invoice, with the amount. From there you buy +1,000, +5,000 or +20,000 runs. At 80% and 100% of the allowance, whoever administers the account gets a bell and e-mail notice. The agent never stops for lack of balance.
Quantities, percentages and measures in Tenkai's answers now use the decimal and thousands separators of your language ("1,234.5 kg" in English, "1.234,5 kg" in Portuguese). Before, some answers mixed "8,5" with "$1,234.56" in the same sentence.
When a release improves a help text, the new text also shows up in accounts that already had that help, in all 11 languages. Help you edited by hand stays as you left it: the release only replaces text nobody touched.
You can now ask with a period: “which webhook failed this month?”, “what changed in the tax reform table this quarter?”, “is what I sold this quarter classified for the reform?”, “how many campaigns did we send this month?”, “who reopened the closing this quarter?” and “which bus trips came this week?”. Without a period, the answer stays as before.
When you ask “who is overdue?”, Tenkai lists each customer only once, with the amount and how many bills are overdue. Before, the same customer appeared twice, with and without the count.
In the Global calendar, removing an event now shows “Event removed from the calendar” with its title. If nothing is removed (the event had already left or comes from another screen), the calendar says so and where to remove it. Before, the event vanished without any message.
On the shop-floor phone, the field inspection and the cash register, a record someone else saved without signal now waits for that person to sign in and uploads by itself when they do. Before, it turned “in conflict” and asked for “Try again”.
When you tap Tenkai's question field on the phone, the chat shrinks to fit above the keyboard and the field stays in view while you type. Before, on some devices, the keyboard covered the field.
When the same brand or character has two license contracts, Tenkai's answer now carries one link per contract, and the License royalties screen opens filtered on it. Before, both links opened by brand and seemed to point to a single contract.
At the POS register, the refusal notice (card declined, amount that doesn't add up, item without stock) stays on screen until the operator closes it with the X. Before, it vanished in seconds, sometimes before it could be read.
In the Owner cockpit, each account row shows the account name when it differs from the company name and flags demo accounts. Search finds by account name (“Grupo Demo”) and by the demo brand, and a link with ?q= opens the list already filtered. Before, Grupo Demo showed up under one of its companies' names and search did not find it.
The retail demo (Demo Mercado Quintal) now opens with the “Ask Tenkai” button at the top, like the other demos. Before, it did not show there.
In Customer 360, the next action, the timeline (contract, invoice, ticket, opportunity, visit) and the statuses (active, paid, won) now show in the reader's language, and money amounts stay readable in Arabic too. Before, part of these texts came out in Portuguese and statuses showed as codes.
The public Help Center shows each screen's full article — steps, rules, FAQ, images and what the screen contains — to anyone, signed in or not. You can send an article link to someone who doesn't use Tenka yet and find answers through a web search.
In the family account, quick search (Ctrl+K) finds only household screens — budget, accounts, cards, goals, investments, debts, income tax — and no longer offers business screens such as card-machine reconciliation, foreign exchange or approval limits. The entries list also stops showing the "Profit center" and "Reconciliation" columns, which are for companies.
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".
The service deadline of each row is no longer checked one by one: the ticket and task lists open with the same amount of reading whether the page has 10 or 50 rows.
The card summary (health, margin and what to offer) now calculates only the open customer, not the whole company — the figures are the same as in the portfolio, and the card no longer slows down as the base grows.
The contract tabs (products, prices, finance, documents, amendments and the others) load when you click them, not all at once when the card opens. What you did not open stays as it was when you save.
When you run the retention policies, the page says how many records were processed, whether nothing had expired, or whether the run failed — before it said "executed" even when nothing ran. The cold-lead grace period now also follows the account's local time.
A line you add by hand to the inventory now brings the item's balance in the warehouse as the expected quantity. Before it started at zero, and the adjustment came out as the whole counted quantity.
In the Customer 360 card, the Health tab (with the partner's Tenka Score), White space and Schedule visit load when you click them, not all at once when the card opens. The partner score now reads only the open customer: the figures are the same, and the tab no longer slows down as the customer has more contracts.
In the contract's products and prices tab, the first column of the packs table is called Product again (the header repeated "Pack" twice) and sorts by the product name.
When you change the language, the line that explains each area of the side menu ("work, projects and hours") now shows in the new language right away, together with the area name. Before, it stayed in the language you signed in with until you signed in again.
In the dark theme, links such as "open" in the Customer 360 timeline and "View in graph" showed in dark blue on the dark background, almost invisible. They now use your company's text color adjusted for dark mode, with reading contrast.
The Terms of Use and the Privacy Policy had two versions in force at the same time, and the acceptance screen could list both. Now each document has a single version in force — the same one shown on the public page — and acceptances already given remain on record.
Statuses like Open, In progress, Waiting for customer, Resolved and Closed now show in the language you read, in the demand list, the board, the demand card, the customer portal, the agenda and the mobile app. A status name your company wrote itself stays exactly as written.
In the Demo Group, each company in the chain now has its industry's margin: cotton gin and spinning mill around 12%, knitting and weaving around 15%, dye house around 20%, garment maker around 28%, sewing contractor around 20%, and the store with a 45% gross margin. Each sale comes from the kilo or piece that actually left, each purchase is the kilo that came in at the seller's price, and payroll matches the size of the operation. The group chain panel shows the group with a 14% to 19% monthly profit, and each company's income statement tells the same story.
In the cutting order, the theoretical consumption is now what the technical sheet says the size grid uses — pieces of each size × the size factor × the fabric consumption per piece on the sheet —, in the fabric's unit (kilo or meter). Before, it showed the piece count with the factor, and a lay of 177 cropped tops showed 184.92 against 45 kg of fabric, with 411% efficiency. Now it shows 40.68 kg and 90%. Without the fabric on the sheet, the theoretical value stays blank instead of wrong.
Dye recipe weighing, the dosing unit, and the laundry take chemicals from the warehouse set in Settings › Dye house; without it, from the company's first stockroom — and never again from a third-party warehouse, which holds the customer's fabric. In the demo, the dye house had its dyes in the third-party fabric warehouse; they were transferred to the chemicals stockroom, with the reason in the stock history.
When you deactivate a person’s access in their record and save, the Users list already shows the “Deactivated” badge, without reloading the page. The list search also moved out of the part that refreshes, so what you type is not lost.
The “Status for the customer” options (Received, In review, Planned for release, Delivered…) show in the user’s language, in the request record and in the list. What is saved does not change.
When the account has no AI turned on, Tenkai delivers the numbers straight from the database in your language: the source, the “check it in”, the notice, the screen button name and the P&L and royalty labels. And when it finds no data, it states the period it consulted (for example, the current month).
In Production by machine you now enter the yarn consumed (which yarn and how many kilograms), the kilograms of fabric produced and the declared loss with its reason. When you save, the loss leaves the yarn stock at that moment, with the yarn lot and the production date — and comes back if you reduce the loss or delete the record. Fabric plus loss never exceed the yarn consumed. The monthly closing in kilograms adds this loss to the dyehouse loss and shows separately the loss that has not left stock yet.
On the dyeing batch, the loss declared on each in-house finishing pass (stenter, compactor, calender) leaves the batch article’s stock as soon as the pass is saved — and comes back if the pass is deleted or the loss decreases. Finishing done by a third party is not written off again: its loss is in the shipment. A company that prefers to only check the finishing loss in the monthly closing in kilograms turns off the parameter "Dyehouse: in-house finishing loss leaves stock right away" in Parameters.
At the end of a sale, the message now follows how it was paid: cash, Pix and debit are already settled; a credit card sale is receivable from the card company in the number of instalments chosen; store credit stays open in accounts receivable. Cancelling a whole sale in Returns now says how many receivables were cancelled and how many items went back to stock.
In Treasury contracts, the monthly rate and the spread are entered as percentages: 1.8 means 1.8% a month. Before, the schedule treated the number as one hundred times larger, and a 1% rate produced installments with 100% interest a month. Older contracts were converted; if you registered a contract after 09/12 following the "0.018" hint, check its rate before generating the installments. If the contract had already generated installments with the wrong rate, check the rate and use Generate installments in finance again: an installment already reconciled is kept.
Sending a treasury contract to the trash now offers Undo right away, and the screen's Trash opens: from there the contract comes back with Restore or goes for good with Delete permanently. Before, the Trash showed an error and the contract did not come back. If the contract had already generated installments, the notice says how many remain in finance.
When you import tasks from a CSV spreadsheet, a description with line breaks, semicolons or quotes now comes in whole, as a single task. Before, each line of the description became an invalid row in the preview.
With no status in the spreadsheet, an imported task starts in the first status of its type’s flow, or in the company’s first open status. Before, it could start in a status such as "Rejected by the client".
If the owner’s name in the spreadsheet belongs to more than one registered person, the row comes back in the preview saying how many there are and asking for the person’s e-mail. Before, the task went to the first one with that name, without warning.
In the task list and in the Squad room, a task with an employee as owner no longer counts as "no owner", and the card shows the employee’s name.
A room with a team shows each member’s tasks and the company’s monthly sprint when the team has no sprint of its own. Cards show the due date and flag overdue ones, "in progress" counts only what has started, velocity shows only the team’s sprints, and only the flow’s columns and those with tasks appear.
In the Squad room’s TV mode, the menu and the top bar step aside and the board fills the whole screen. Before, the menu stayed and the board dropped below the screen.
In lists, bulk actions (trash, restore, delete permanently, bulk edit) act only on the rows selected in the current search, on any page, and the counter shows all of them. Before, a row selected in an earlier search could go along without showing.
In the task spreadsheet, a row with no type (or a type that does not exist), and one missing the client and product its type requires, come back in the preview with the reason, and the other rows are imported. The client is now also found by legal name and tax ID.
Saving a task that already has an employee as owner no longer puts you in their place, and the task board shows that employee instead of offering "Take it".
In date and date-time fields, the error message names the field and shows an example in your format, such as "12/31/2026 6:30 PM". Before, the date-time field showed a code instead of the name.
Ask Tenkai "what is the squad velocity?", "how much does the team have in progress?" or "is anyone over the limit?": it answers with the open sprint, work in progress against the limit, who has the most tasks, what is stalled or has no owner and the velocity of the last sprints, with a link to the room. All in the same place as each task’s client, contract and hours.
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.
The approval limit for retailer penalties is read in the company currency: a company in dollars sets its limit in dollars in the settings. Without the setting, the default of 5,000 reais converted at the day rate applies. The acceptance dialog shows the limit and the currency.
The case and pallet label shows case and pallet in the language of the shipment customer. In the license, choose the licensor language: the Report to the licensor button downloads the period spreadsheet with headings in that language.
A closed extended producer responsibility period can be reopened: write the reason and click Reopen. The period leaves the closed list, the reopening stays in the trail (who, when and why) and you close it again with the corrected numbers.
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.
Defects marked in the roll inspection, with their position in meters, now go into the cutting plan: the stretch around each defect is left out of the lay, plies are calculated from the usable length and the plan warns which roll has defects and where. In the roll reconciliation, the loss from defects is shown apart from the table loss and from shrinkage.
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 is bought by the kilo and cutting measures in meters. Now the tech pack line can be written in meters (or kilos), and the garment cost converts by the meters per kilo measured on the lot’s rolls — not by a fixed number. Material planning and the production order consumption use the same conversion.
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.
When you enter the surplus invoice on the exchange, Tenka gives the right CFOP: sale (5101 own production, 5102 yarn bought for resale), transfer between head office and branch (5151/5152) or no value (5949) — 6xxx across states — and the buyer’s entry carries the mirror (1101, 1151, 1949…) with the invoice and the inherited lot.
Four finishing touches: the "Fusing (interlining)" stage appears among the suggested stages of the tech pack routing and the shipment; the Operations library calculates the thread meters of each operation from the stitch type and the seam length; the advance shipping notice gets the unloading booking at the retailer DC (window, dock and reference, highlighted when it is after the promised delivery); and the size grid and the label show the size in EU, US and UK for exporters.
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.
The buttons that create a purchase order (dyes and chemicals for the queue, and production MRP) now create one order per supplier, each product with the last supplier that sold it. A product never bought before is named in a warning before saving, so you can choose the supplier on its first purchase.
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.
When the order takes items from the 2nd-quality stock, the warning appears at the top of the form, listing the lines, instead of the corner pop-up that sat over the Save button. Check with the customer and save again to confirm.
In the drawback concession list, the Open duty column shows "(estimate)" in the cell itself whenever there is a value, not only in the footer. The figure is proportional to the exported value; check the official report of the concession before paying.
A design whose name already starts with the word "Design" appears only once in the save, trash and restore messages, and in Tenkai answers about embroidery.
In the simulated EDI exchange, an order pasted on screen now produces the receipt acknowledgement and the order reply already marked as sent, noting that nothing left the company. Before, they stayed as generated until the next cycle.
Ask "what is delaying production most this week": Tenkai answers the step where lots are stuck, how many days the oldest has been there and how many lots are past the planned date, with the days late. What delays delivery comes first.
When the answer has a bar chart, the table with the same items stays available for export and screen readers but is no longer repeated under the chart. And if the wording repeats the same line, it appears only once.
When a drawback concession expires with a balance still to prove, Tenkai’s answer always gives the number of days since it expired and warns that the open duty becomes payable.
Ask "how much did we spend on expenses by category?" and Tenkai adds up the period’s expenses by category, largest first. The answer and the spend by supplier follow access to finance: anyone without it is told their profile does not reach the subject, instead of "not found".
Ask "which EDI orders have a GTIN without mapping?": Tenkai lists each held order with the retailer’s number, the channel, the day it arrived and the missing codes. When there are none, it says there is nothing pending. List questions about the network exchange also bring the items, one per line.
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.
Type "embroidery design", "embroidery stitches" or "cost per thousand stitches" in search (Ctrl+K) and the tech sheet shows up, with the Embroidery tab. Tenkai understands the same words and answers the embroidery cost of each garment.
In the textile demo account, the embroidery design, the embroidery file and the production order for this week’s delay start with EXEMPLO_, so no one mistakes sample data for real data. The demo script now shows the seven October additions: conditioned yarn weight, fabric yield, roll resting, embroidery, price by channel, 2nd quality and drawback.
Twenty-five weaving, knitting, dyehouse, spinning, collection and HR screens now have in their help the frequently asked question about the most common error of each (why saving was refused, why the button doesn’t appear), and the screens that had only one explanation got a step by step. In the sample 3D viewer, the tip now tells how to rotate and zoom with the keyboard.
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.
The Night planner proposes the dyehouse and knitting schedule overnight. It can now be hired only when the company’s plan includes that module; without it, the agent catalog says why and what to do, instead of hiring an agent with nowhere to work.
When you finish, the cart dims and "Saving the sale…" appears until the sale goes through; then the cart empties and the change shows. Before, the cart stayed full for a few seconds and it looked like the sale had not gone. Closing the register also locks the count and shows "Closing the register…" until it is done.
In the counter POS, F9 (or the Close register button) opens closing with the cursor already on the first bill count field: just type. Before, on a freshly opened page, the count did not take what you typed until you clicked the field.
Once you answer or dismiss the 30-second survey, it does not come back every time you sign in. It does not show in demo accounts.
In the Operations library, thread per piece is now called Estimated thread and explains where the number comes from (the thread makers' rule, not a measurement of your seams). On the item size grid and on the label, the EU, US and UK size carries the note "conversion reference, check with the customer".
While the company has not turned on the refusal of issues without stock, the issue and the transfer show a discreet notice: the balance may go negative (it is flagged on the Stock dashboard) and the refusal is turned on in Parameters. On the mobile register, the help explains what happens to an offline sale that uploads without stock: it stays in the queue with the reason and uploads only once after the authorization.
The low-score subcontractors card opens Credit score with only bands D and E; the predictive alerts card opens maintenance with only the machines in alert; and, in the real margin by channel, the number of orders opens the channel's orders list over the same period. Whoever doubts a number sees the rows behind it.
Under Diagnostics ▸ Content, the platform shows how many release-note, help and assistant files were applied, and warns when any is missing. If applying fails at startup, it retries and records the reason.
When a card sale at the register cannot post its receivable, the alert reaches whoever handles reconciliation again and opens the card-terminal statement list directly.
In Diagnostics ▸ Content, Apply what is missing now runs in the background: the screen answers right away and, on reload, shows how many files are already in and the summary of what was applied. Before, the screen was stuck for several minutes.
On the Legal tables screen, the line for withholding tax on royalties paid abroad (15%) shows Provisional Measure 2,159-70/2001, art. 3, in the original publication by the Chamber of Deputies, with the link and the date it was checked. A beneficiary in a country on the Federal Revenue favored-taxation list pays 25%, also calculated.
On the sales order line, choosing the certification shows how much is free for this order (the balance minus what other open orders already reserved), the lot list shows only lots with an incoming transaction certificate for that certification, and the system tells you right away what would block the sale. A line that would not fit does not enter the order.
In the sales order entered at the office, the total quantity of each item (all colors and sizes) picks the tier of the customer price table, as already happened on the retailer portal and on the sales rep phone. The line shows the tier reached, how much is missing for the next one and the lowest price the channel accepts; a price you typed by hand is not replaced, and a discount that breaks the margin floor needs approval.
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.
Mark the garment audience as MASCULINO on the product attributes tab: the size grid, the label and the assistant convert men’s numeric sizes (BR 40 = EU 48 = US 32 = UK 32). Women’s garments, adult without gender or with no audience stay on the women’s table (BR 40 = EU 38 = US 8).
The help for counting on the phone, picking in the store and the SEFAZ services now has the frequent questions about the most common errors: a code that is not any piece, a piece outside the list, a count already applied, a piece of another size, an ID that does not match, a piece that already left and a SEFAZ address that stopped invoices.
In the Dye lot and the Dye recipe, the options for Mode (exhaust or continuous), Substrate (knit, woven, yarn on package) and Continuous process (pad-steam, pad-batch, thermosol) now show in the chosen language, as the field names already did.
Name, staff number and embroidered name of people on the uniform list disappear on their own 180 days after the contract ends or the person leaves (you set the period in Parameters). On the Privacy screen, the person on the list has a data report and anonymization, and admissions through the portal and size changes are recorded with who did it and when. The broken needle note is erased after one year; the record stays.
The DARF for the income tax withheld on royalties to a licensor abroad now falls due on the day the royalty is credited (when the payable is created) or remitted, whichever comes first, as the law requires. Before, it fell due with the payment to the licensor and could be late.
With the no-stock refusal turned on, the register now checks stock before saving the sale: without stock and without an authorization from the Stock panel, the sale is not saved and nothing is charged. Before, the sale was charged and stock fell behind. A sale made offline on the phone still uploads and reduces stock, because the item has already left.
When a receipt arrived on top of negative stock, the item's average cost could multiply (one fabric went to R$ 1,780 per kilo). Now, with zero or negative stock, the average cost becomes the receipt's own cost. The Stock panel also opens faster.
The dye house, the sewing contractor and the store now show what came in and went out (batches and pieces). And when an intercompany order exceeds what the seller invoiced, the cockpit says which company to check instead of silently dropping the group's revenue.
Royalty bills abroad (licensor, income tax, CIDE, PIS and COFINS) now fall in the month the royalty happened, and the description cites the DARF code without amounts. Saving the license, creating the bills and closing the period are for people who can change accounts payable, and the licensor report is only for those who see amounts.
Recording a call-off delivery now creates the order and the invoice exactly at the contract price, with no club discount and no companion item, and the receivable stays linked to the contract. The delivery's e-invoice also no longer fails when sent.
On the sales order, the quantity-break table for the Wholesale channel and the customer's own table now apply as soon as you choose the channel and the customer, before saving. And the purchase order created from chemicals or planning goes out with the products that have a supplier and flags the ones left out.
On an invoice that has not been transmitted yet, the "XML preview" button shows the XML that would go to SEFAZ, with the complementary information (including the certified sale's certificate number), unsigned and with no tax value. You can check it before transmitting, even without a digital certificate.
The help on the API keys screen shows how to read only the rolls that changed and how to send rolls to the processor without duplicating the shipment, with the call ready for whoever integrates.
In a licence with a licensor abroad, the withholding tax is now 25% when the country is on the Federal Revenue favored-taxation list (otherwise it stays at 15%), and the statement preview says which rule applied and why. If you mark that the remittance includes a technical service, payables for PIS and COFINS on imports are also created, to be paid by DARF. The IOF on the exchange shows as an estimate, because the bank charges it. A tax treaty with the country and a privileged tax regime remain with your accountant.
If a store PIX charge through the provider stays pending for hours without the payment notice, or a card machine approval gets no answer from Stone or PagBank, the integrations hub and Tenkai show the warning with what to do. The sale never locks because of it. The time limits are in Settings, PDV group.
On the owner's Home, when Tenkai is off, the Meet Tenkai button takes you to Settings > Artificial intelligence. Whoever cannot change settings sees who to ask.
In the last 30 days result, clicking the Came back or Bought number shows the customers of that rule, with the message date and amount, and each name opens Customer 360.
On the order link, the customer only sees the items that can still come back; one returned in a completed exchange leaves the list. Asking for the exchange twice, in two tabs, does not open two: the second gets the notice that one is already in progress.
The markdown suggestion now adds up sales only for items that still have stock in the stores, not the whole register history: the screen opens faster, with the same suggestions in the same order.
When you click the Came back or Bought number, the customer list now also shows the channel, the message sent and the day it was sent. You see which message brought each customer back. The list goes to a spreadsheet through the table export button, and the dialog got a Close button.
On the Rolls screen, the Rate source column now shows, right below, where the moisture rate came from (the standard or the supplier contract, with the reference and the lot). Before, it only showed on mouse hover and never on the phone. The agreed rates window also fits the phone screen.
The Timeline tab of Customer 360 now lists the clienteling messages the customer received, with the rule, the reason and whether she replied or bought. At the top of the tab, the amount that came back through clienteling in the last 90 days opens the clienteling screen. You can also ask Tenkai how much clienteling brought back this month.
The Privacy screen has a panel for whoever requested the demo with name and e-mail. From there you export that person’s dossier or erase their data, as you already do with customers and employees.
In Data retention (LGPD), the cold leads policy is turned on with 24 months in every company that never changed it. It takes effect 30 days after the update and the screen shows the date: if your company does not want to anonymize, turn it off and save before then. Anyone who had already turned it off stays off. A cold lead is a contact with no interaction for longer than the period.
On the Rolls screen, the yarn conditioned weight now shows the source of the moisture regain: the ASTM D1909 standard, the European BISFA table or the supplier contract. In Settings the company picks the standard; in Rolls it records the rate the contract fixes per supplier, fiber and lot. The lot contract beats the supplier contract, which beats the standard, and the invoice and the weight claim state the rate and the source used.
When you settle a bill for less than its total, the bill is settled for what came in (and counts in the day's realized cash) and the balance becomes a new open bill with the same due date and the description "Balance of: …". The notes on both say where each came from. Before, the whole bill was marked paid and the balance vanished from receivables.
If the bill's accrual month (or the due date, when there is none) is closed, settling and Undo settlement are refused with the reason on screen. To change it, reopen the month in Monthly closing. Reconciliation already followed this rule.
If any shipment line has no outgoing warehouse, Ship refuses before moving anything and names the lines: choose where it ships from on the sales order ("Ships from" field). If a line lacks stock, the shipment is not marked shipped and the message lists what was missing. Before, the line was skipped and the order showed shipped without leaving stock. The cost of what left goes to the income statement right away, even when another line of the same shipment fails.
Opening a sent, accepted, declined or expired proposal shows at the top that it can no longer be edited because of its status. When acceptance creates the contract, the contract now points to the originating proposal, and the accepted one-time amount goes to the opportunity, which adds up in the pipeline.
In the group chain cockpit, the sewing contractor link now counts pieces when no batch has closed yet, instead of showing zero kilos. When batches close with their output weight, the link goes back to weighing by kilo.
When you settle only part of a bill split across cost centers, each center keeps its paid share on the settled bill and the remaining share moves to the balance bill, in the same proportion. The cents add up: across both bills, each center has exactly what it had before.
The bill's Settlement tab now shows the trail: who settled it, who made a partial payment and who undid the settlement, when, and with which amounts. Undoing is still possible, but it is recorded. And if the bill had been split by a partial payment, the message gives the number of the balance bill, which stays open.
When a shipment cannot go out because the outgoing warehouse is missing, or because an item had no stock, the message now shows the item code and name (before it showed an internal number that appeared on no screen) and arrives in the language you chose.
In shipping, inventory count, packing list, stock movement, production order, store transfer and received consignments, the buttons that save (ship, check, apply, release, record, complete, return and others) now respect your profile permission on the server too. Someone with view-only access gets the notice that they can see but not save, and nothing is changed.
When the client accepts the proposal, the contract is created with the accepted monthly amount, points to the proposal it came from and gets an obligation "Charge the one-time amount of …" with the agreed payment terms, so the setup fee is not forgotten. If the contract cannot be created, the acceptance is not recorded either and the message says why — before, the acceptance could be saved without the contract being linked.
On the proposal link, the accept button now asks for the name and CPF or CNPJ of the person accepting on behalf of the client; the document is checked. Both are saved on the proposal and, on the generated contract, the person is recorded as the one who accepted, with the acceptance date. It is a record of acceptance, not an electronic signature. In the client portal, the signed-in client is the one who accepts.
When you convert a lead that has a company, the client now gets the company name and legal name, and the lead person becomes the client contact. That way Client 360 and the invoice carry the right name. A lead without a company still becomes a client with the person's name.
On the pipeline board, each column now shows the total with the one-time amount added to the recurring one and the value weighted by probability, the same as the sales dashboard. And the opportunity history says from where to where: the previous and new stage, and the value before and after when it changes.
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.
Buttons that save now respect what your profile allows on each screen: creating needs "Add", changing needs "Edit" and removing needs "Delete". If something got blocked for you, an administrator grants it in Access, in your group, on that screen.
Anyone who enters a Free, trial or under-30-day account and browses like a robot (dozens of screens without doing anything, machine pace) gets a one-click challenge; failing two challenges blocks the account for one hour and the account administrator is notified. Paying accounts get more tolerance and are not blocked: the administrator gets the notice and decides. Accounts under evaluation export up to 20 times a day, and the file carries its origin.
Opening the register now requires the same profile as selling and closing. Before, a profile without edit permission could open the register and get stuck, unable to sell or close. Gift card sales also respect the profile now, and the out-of-stock refusal names the item, the balance and the order.
In stock movements, the Authorize button for out-of-stock issues refused everyone, even those with permission. Now the Stock movement permission itself applies: whoever can edit and add there authorizes the issue, with the usual reason and validity.
In a list, when you send several records to the trash at once and one cannot go — closed stock month, read-only profile or link to another record — the message now gives the reason, as it already did for a single record. Before, it said "unexpected error".
Sending a proposal with no items is now refused, with a notice to add at least one. Before, it got the public link with a zero value and the client received an empty acceptance.
When registering a silhouette in the showroom, the drawing field accepts only the outline (path commands and numbers). Any other text is refused with a notice, because the drawing shows on the showcase the client opens by link.
When the proposal validity date has passed, the client link says it has expired and offers no Accept button, and sending it asks you to adjust the validity first. Before, an expired proposal could still be accepted.
In the Customers recycle bin, Restore showed "Record restored." but the customer stayed in the bin, and Delete permanently did not delete either. Now both buttons do what they say, and when nothing changes — the record already left the bin or belongs to another company — the list tells you nothing was saved.
On the shop floor, at the till and in the field, records made without a connection stay on the device. Before, if someone else signed in on the same phone, the record was uploaded under their name, and a rejected downtime reason could turn into the warning text. Now each record uploads only when the person who made it is signed in, the warning is kept apart from what was typed, and phone buttons show the confirmation or the reason for a refusal.
In a company that has not set up calendar layers yet, saving a new event showed "Internal error". Now the event goes into your own calendar, and people who can only view the calendar see the create, save and remove buttons disabled.
In Exchanges and returns, registering the exchange of a POS sale ended in "Could not register the exchange" and nothing was saved. Now the exchange saves, the voucher is issued (or the cash leaves the till, for a return) and the items go back to the stock of the chosen warehouse.
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.
When a register's approval is removed, the numbers reserved for it close immediately. An invoice issued by that register afterwards becomes a pending item, and whoever sees invoices gets a bell notification right away.
If the same invoice issued offline arrives twice, the second one becomes a pending item that says which sale already holds the invoice.
If the system cannot check a sale coming up from the register's queue, the sale stays stored on the register and uploads by itself later. A sale with more than 200 items asks to be split instead of uploading only half.
Under the standard tax regime, an item with tax substitution or a reduced tax base appears in the to-do list, with its name and the way forward: issue through your tax provider or adjust it with your accountant.
Ceará stopped using the MFE and counter sales now go out with the NFC-e. With the A1 certificate and the company accreditation, Tenka issues the NFC-e directly with the state tax authority, even when the register is offline, and sends it later.
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.
If the phone and the internet flicker and the same sale uploads twice at the same time, it is recorded only once and the customer's voucher or credit is deducted only once.
A sale that couldn't upload because the system was down stays stored without an error mark and retries by itself later. Only what needs someone to fix it goes to "with error".
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.
The approval the card machine sends is checked before the sale is paid. An approval that doesn't match is rejected. While Stone or PagBank have not confirmed it to the system, someone with authority checks it on the card-machine portal and releases it, and who released it is recorded.
Closing on the phone counts cash, Pix, debit and credit without showing the expected amount first, records the difference per method and e-mails the Z reading. Once closed, the register can't sell.
The printer menu shows how to pair, the 58 or 80 mm roll and the test print. On iPhone or Firefox, it says the receipt goes by WhatsApp or SMS.
When you record the contractor's advance in Produce right, Pay per piece tab, the cash outflow is created with it. Removed the advance? The money returns to the cash box with a reversal, and nothing disappears from the statement.
If the advance exceeds what the contractor has to receive, the closing deducts only what fits and the rest stays open. The payment is never negative.
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 the closings list, the arrow opens the lines: service, defect discount, advance, trims and each tax withheld. The sum is the bill amount.
The self-employed receipt and the payroll withhold social security by the 2026 brackets (cap R$ 8,475.55), income tax with the right deduction (the simplified discount replaces social security when larger) and the new law's reduction for earnings up to R$ 7,350.
A return the contractor proposed through the link that nobody checked within the deadline (2 days, adjustable) notifies whoever checks returns in Outsourced processing.
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.
An individual contractor sees on her link, even before the first payment, that she is paid by receipt and does not need to issue an invoice.
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 the Essential profile, the product and customer forms open with only what matters. "See complete" shows the rest and the choice is saved.
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.
For a cut that came from the plan, each roll's reconciliation shows the planned plies and metres next to what was measured.
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.
A marker the CAD sends with a style code Tenka does not know appears in Cutting plan, Markers without a style. Say which style it is and the consumption goes to the tech pack.
The "size;consumption" file with a decimal comma (S;0,42) is now read as 0.42 m; before, the number was split at the comma. With the quantity column ("size;quantity;consumption"), the marker also stores the pieces per ply.
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.
Whoever scans the label QR sees the certified fibre and the transaction certificate number, to check with the certifier.
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.
No VAN contracted yet? Create the channel as "Simulated VAN", paste a sample order and see the whole flow without anything leaving the company.
In the retailer's penalty, its order document links the penalty to the order that came through EDI. The dispute already has what was ordered and when.
For Shopee, Shein, TikTok Shop and Mercado Livre, when the seller account is connected, the listing is only approved with the composition adding up to 100%, the care instructions and the country of origin from the label, which the marketplace requires and inspectors check.
If the VAN does not respond for more than two cycles (30 minutes), the integrations hub shows the warning.
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.
A QTX file that only carries the reflectance curve (400 to 700 nm) now becomes L*a*b* under daylight (D65), store light (TL84) and incandescent (A). Before, it was rejected.
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.
The standard defect catalogue arrives in the language of whoever imports it.
Adjust the milestones and days before delivery in your company's template; new critical paths are created with it. And the late-delivery warning arrives every day, without opening the screen.
"How much can I buy" now counts the cost of completed production orders as actual spend, not only paid purchase invoices.
The simulator per supply-chain link shows each link's PIS/COFINS and IPI until 2026 and zeroed from 2027, as the reform amendment requires.
The contractor's link shows the risk score terms: what it uses, that it never decides anything on its own and how to ask for a review. The acceptance is recorded with the date and version.
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.
In the bale's origin report, upload the lab PDF right there: it goes to the documents and is already linked to the report.
The contractor check accepts the government list's official PDF, as it is published.
In the seamstress's closing, unjustified absence and social-security leave remove the day from the proportional wage floor; medical certificates and vacation do not. The calculation shows how many days.
On the privacy screen, an individual supplier (the contractor, the self-employed) can receive a file with their data and be anonymised; the contractor network's data has a retention period.
The daily customer win-back list shows each saleswoman her own customers; management sees all of them and whose each one is.
A tour guide's commission above the company cap is only paid with the e-mail and password of someone who can authorise it.
The customer's order link and the tour agency link keep working, but not even someone who sees the database can build a link. "Agency link" generates a new link every time.
Selling at the till an item set aside for another order requires authorisation from someone who can give it; and a card sale that did not become a receivable is flagged on the bill for reconciliation.
A production issue with no balance and no cost is now rejected with the reason: record the receipt with its cost first.
In the Help centre, the implementation guides for garment makers, sewing contractors, spinning, dyeing and stores include this version's steps: cutting plan, productivity benchmark, transaction certificate, experience profile, first piece, forecast, laundry, bale with QR, the contractor's receipt and the register approved to sell offline.
In Produce right, Pay per piece tab, the "Yes" of Close and post saves the contractor's closing with the bill, the receipt and the deduction of the cash advance and trims. Before, it could answer "Nothing to pay" even with a value in the preview. The card now shows the service, the deductions and the net to pay, and the button stays off when there is nothing to close.
The cash advance to the sewing contractor leaves the company's Cash account (type Cash / Money) and its balance changes right away; if the advance is removed, the money returns to the same account. With no Cash account registered, Tenka creates "Cash" the first time.
The automatic profile now looks at what the company does: apparel, sewing contractors and stores stay in Essential, even on a larger plan; spinning, knitting, weaving and dyeing stay in Complete. The menu's Most viewed follows the same rule and no longer brings industry screens to those in Essential. "See everything" still shows it all whenever you want.
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.
Saved the yarn lot's test report, weighed the rolls off the loom or released the dye lot weighing? The proof for that step is stored right away, linked to the previous one. Nobody has to remember to record the evidence.
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.
When a cut comes from a cutting plan, the cut's proof keeps the plan, the lay and the CAD marker used. Swapping the marker file afterwards does not go unnoticed.
Fabric sent out for dyeing or finishing now shows in the passport as a dye house step, no longer as a sewing contractor.
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.
Replenishing the test batch respects the forecast for each size and colour, and the total respects the item's: restocking 300 of size M when the M forecast is 120 left stock sitting idle.
The storefront link and the catalogue addresses for Instagram, Facebook and Google keep opening as they are. From now on the link is shown only once: when the store is created or when you click "Generate new link" — copy it right away. Generating a new one stops the old one from opening (also replace it on Instagram and in the Meta and Google catalogues). With a verified custom domain, nothing changes.
Public links from a demo account (booking, proposal, catalogue, tracking, passport and the rest) show the demo banner; the booking page does not schedule the meeting and the catalogue neither records orders nor sends codes by WhatsApp.
When the card fee or NSU is not applied, the sale's receivable carries the pending note: at the register with or without an integrated card machine, on the mobile register, when invoicing a debit order and on gift cards. Before, only at the register with an integrated card machine.
Selling on the mobile register an item set aside for another order asks for the email and password of someone who can authorise it, just like at the counter register.
Tours saved with only the guide's name now show the guide in the "Guide (commission)" field, so the commission has someone to go to. At the register, the selected tour no longer resets to "none".
Buttons, links and tabs in the company colour stay readable on mobile, on public pages and with any brand colour, in both light and dark themes.
A phone authorised as a register stopped signing in after 30 days, even when used every day. Now each use renews the period: only a device left unused longer than the validity asks to sign in again. Disabling the device or the user still removes access immediately.
Windows that open over the screen, such as help, the knowledge base and the "Help us prioritise" survey, close with the Esc key, and the cursor returns to where you were.
On the public garment passport and bale pages, secondary text is more readable, the page speaks the visitor's language and "Verify now" is now a large button that works from the keyboard.
The key stored on the phone to issue invoices offline is now stronger and tied to that device: copied to another one, it does not open. A phone prepared before this version asks to be prepared again, once, with internet.
In the Studio, projects, agenda, contracts, legal cases, the mobile time clock, the owner's cockpit and the client portal, hours appear as "1h 30min" instead of "1.5h".
In Tenkai's answers dates follow your language's format (12/13/2026 in English) instead of 2026-12-13.
Registering a marketplace channel (Shopee, Shein, TikTok Shop) in Sales channels saves again; Save used to fail with an error. Selling through it depends on each marketplace's seller account being connected.
In your user menu, "Follow the company (automatic)" clears your choice between See everything and See the essentials, and the menu follows the company setting again.
In Piece-rate payment, the contractor preview warns when an open cash advance or trim is dated after the period end: it does not enter this closing and stays for the next.
In retail EDI, a deleted channel can be undone right away from the Undo bar and shows up under "Channels in the recycle bin" with Restore.
A VAN SFTP address pointing to the internal network (localhost, 10.x, 192.168.x and similar) is refused when saving the channel, with the reason on screen.
In the Cutting plan, cutting a lay now creates the cutting order with the pieces in stock, marks the lay and closes the plan together. If something fails midway, nothing is saved and the rolls stay in stock — before, the rolls left and the order stayed empty.
A plan not yet cut goes to the bin with Undo, and "In the bin" in the filter brings it back. Proposing again for the same order replaces the previous proposed plan. The fabric shortage warning tells the shade band of the rolls.
In the Dye house, "Schedule from light to dark" no longer stops when a batch is larger than every machine: it shows under "no machine" with the reason. The "in process" number on the panel now counts the same as the list of batches in process.
On the mobile payslip, "How the income tax was calculated" opens the math: the table used, the base, the chosen deduction and the Law 15,270 reduction. The reduction now comes from the Legal tables screen, and the payroll period warns when a table is missing or expires within 60 days. Withholding bills are not created in a closed month.
In the closing count, if the counted amount does not match, the count locks, the difference by method shows and the register only closes with a written reason — and whoever reviews gets a pending item in the bell with the register number. A closed register no longer sells online, and a sale made offline that uploads after closing shows in the reading as "came in after the Z reading".
The phone now uses the same price table as the desk register, even offline. A sale that uploaded leaves the queue at once (the "in queue" badge goes away) and a double tap or the Pix confirming at the same time do not send the same sale twice. At closing, each method shows as "Counted".
The phone times screen says what it is: the record of your activities for team management. It does not replace the company's official time clock, and the text no longer talks about "punches".
On the public passport page, "Verify now" tells how many links of the garment check out and, separately, the total counting the fibre origin — the same number as the summary above.
Questions such as "which EDI orders have a GTIN without mapping?", "which offers are on the capacity exchange?" and "how many warp beams run out in 8 hours?" now come back with the answer, even when the AI does not pick the query. When a query does not finish, the answer says which one — no more unexplained "I couldn't answer" — and internal query names no longer show.
In EDI with the retailer, a link carrying the document number (from Tenkai or an indicator) shows only that document's, interchange's or order's messages, with the filter notice and a "Show all" button. The receipt reply (CONTRL) shows as "Reply read", no longer as "Order created".
When closing the register, if the count doesn't match, the difference shows and the register only closes with a written reason — at the counter POS the field appears in the closing itself (before, the window vanished), and on the phone register too. The Z reading goes to the e-mail queue and the screen says whether it went or why not; a sale made offline that synced after the Z shows in the register reading when you open the POS.
In the Cutting plan, "Cut this lay" with the full size run (XS to XXXL) puts the pieces into stock in one go: each extra size barely adds to the wait. The outsourced sewing cash advance always comes out of the register of the advance's own company.
The public passport page (the label's QR) reads the evidence chain stage by stage and opens faster. The summary counts the chain's stages, from field to garment, and "Verify now" counts the proofs that check out — before, both said "links", with different numbers.
When posting a voucher or trim, subcontractors registered in another company of the group, which already showed in the list, are now accepted. Before, the screen said the subcontractor was not found.
When you ask "what is the passport chain?" without naming the product, Tenkai shows the most recent passports, each saying whether the chain is intact. With a code next to the name ("basic t-shirt 30/1"), it finds the piece anyway.
When Tenkai cannot answer for lack of permission, the subject appears mid-sentence in lowercase and without a cut-off word.
A dyeing batch that already had a color reading used to freeze when switching tabs (Color, Additions, Finishing). Now it opens and switches normally.
The cards on the Today screen used to do the same calculation twice on the first opening; now they do it once and show up sooner.
Without saying which piece, Tenkai shows the most recent passports, each saying whether the chain is intact.
A retailer order file above the limit (5 MB by default) is rejected on arrival, with the reason on screen and the rejection sent back to the retailer. Large orders within the limit, with thousands of items, come in without weighing on the system.
Choosing a GPT 5 or GPT 6 model in the AI settings used to show an unsupported model warning. Now Tenkai talks to these models normally, including looking up system data, and the usage of each question is still recorded.
Imports, integrations and automatic routines of an account with its own database used to be refused. Now they run in the account's own database, without slowing the screens down.
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.
The shrinkage measured in the incoming roll inspection now counts in the cutting plan: a batch that shrinks 3% raises the planned meters by 3%, and the plan shows how much came from shrinkage. In the roll reconciliation, the cutting order separates what was knit shrinkage from what was loss at the table.
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.
On the Embroidery tab of the tech sheet, a deleted design goes to the recycle bin: Undo brings it back at once and the pattern recycle bin lists deleted designs with Restore. A design used on the routing of an active tech sheet cannot be deleted, and the message says which sheet and which step use it.
In Rolls, the conditioned weight by lot and yield by supplier tables show the 30 most recent. When there are more, "Showing 30 of N" appears: filter the roll list by item or production order to see the others.
In the drawback list, the balance to prove and the tax due carry the "(estimate)" mark: proof is calculated in proportion to the value exported in US$, not by the NCM of each good in the act. Check the official act report before paying or requesting closure.
Dyeing recipes now have items: each dye and auxiliary from stock with its concentration. Each batch's quantity is calculated for you and the budgeted cost sits next to the actual.
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.
The batch's Colour tab reads the sample against the recipe's target colour, using the customer's formula (CMC 2:1 or CIEDE2000), shows where the colour drifted and accepts the spectrophotometer file in the accepted format, described in the help. Roll inspection uses the same calculation.
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.
Releasing the weighing, adding to the bath, saving what the dispenser weighed and warping the beam now refuse the withdrawal when the warehouse has no balance, and the message says which item is missing. The older outflows that still accept a negative balance go out at average cost and warn you.
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.
Scheduling refuses a machine that does not fit the article and shows, per machine, the queue days and the sequence that groups the same article and shortens changeovers. One click applies the sequence.
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.
The lab report accepts the count in Ne, Nm, tex, dtex or denier and shows all five units. Filament (POY, DTY, FDY) gets the number of filaments, intermingling and the microfiber warning.
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.
Each warp beam's shade now comes from the color reading of the indigo lot and is no longer typed into the beam. So the warning of a shade jump between beams on the same loom uses the same color math as the dye house, with the customer's tolerance.
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.
When Tenkai reads the defect photo in the phone inspection, the usage now goes to your company's AI account, with your own key when there is one and within the monthly cap you set.
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.
Whoever closes output twice a month now sees both amounts in the payroll. And when an amount does not go in (the month’s payroll not yet open or already closed), the screen says why instead of just saying it is pending.
In the collective agreement, the list with the name and salary of everyone below the wage floor only shows to people with the salary history profile.
If the production closing is run again, the top-up to the wage floor and the weekly rest pay that were not yet on the payroll are posted, without repeating what is already there. With the floor guarantee switched off, the calculation notes say "floor not applied".
Allocation under shortage, network exchange, critical path, foreign trade, collective agreements, the dyehouse, knitting and weaving panels, test and replenish, packing list and the other screens checked on screen no longer show the "under validation" tag.
In the dyehouse, knitting and weaving panels and in the collection open-to-buy, each number opens the list that adds it up, for the same period. The right-first-time and second-quality alerts follow the limit your company sets in Parameters.
Before releasing a batch weighing you see how many products and kilos leave stock. In "View data of", each unit shows its company, and the group chain panel has a button to see all companies and no longer counts twice what one sold to another.
When you open a contract from another company in the group, the License and royalties tab shows that company's license, settlement and seals — not those of the company selected at the top.
In the demo account, the Spinning mill sells yarn to the Knitting mill and the Knitting mill sells greige fabric to the Apparel company: the chain cockpit shows these sales and warns when the price was below cost. Dyeing batches and Home also open faster.
The maintenance order opened by spindle monitoring, the cell or predictive maintenance now has a number, a service deadline and its origin, saves from the form without asking for customer or product, and shows up in the Daily queue of whoever can take it, as "To take".
Without an AI key configured, questions such as "how many items does recipe RX-MARINHO have?", "what offers are on the capacity exchange?" or "what is 150 denier in Ne?" go straight to the right query and come back with the number, the source and the link to the list — without the AI wording and without announcing a model that did not answer.
A new chargeback saves without error, the retailer appears by name in the list, the record and the export, the bill field lists only that retailer's receivables and, when accepted, the expense is due today and joins the retailer's netting of accounts.
With no signal, the stopped machine reason, the bundle ticket entry, hours and spinning entries are kept on the device and upload by themselves when the connection is back, with a pending notice. The install invitation and the tour shortcut no longer cover the field you are filling, drop-downs fit the screen and every button is finger-sized.
When a screen does not open, the message says which lock stopped it: your access group, the company plan or the area reserved for the platform team. The garment passport the customer reads through the QR says there is a supporting document for each stage, without showing the internal document number.
The 20 new garment and store screens (fiscal assistant, mobile till, trips, my stores, store transfer, sewing contractors and others) no longer show the "under validation" tag: they were checked on screen before going live.
The help (the question mark in the corner of each screen) on the new garment and store screens now has the step by step with the names of the buttons you see, and frequent questions such as "why did Send refuse the item?" and "which message uses credit?".
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.
The store transfer moved from where it was born in the menu and now sits with inventory and stock counts, in the stock group, where people look for it.
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.
In Garment production, the monthly sewing shop settlement came out as zero and did not close when "Price per operation" had no "Facção" line. Now the per-piece price you agreed with the shop in the Sewing shop plan also applies — and the calculation says where the price came from. With different prices per operation, add "Facção" to Price per operation.
The calculation that explains the seamstress and sewing shop settlement, and the one on the freelancer receipt, showed numbers in a fixed format like "4.8 = 115.20", started with the code "FACCAO" and showed up even with "Hidden values" on. Now it reads "Sewing shop · … 4.80 = 115.20" in your language (on the receipt, the language of whoever receives it), and with hidden values the calculation is hidden like the totals.
On the owner's Home, the "Ask Tenkai" button showed even with Tenkai turned off for the company, and clicking did nothing. Now it only shows when Tenkai is on.
The Federal Revenue company base behind Prospecting stopped at its last step and the search came back empty. It now loads to the end: after the next base update, searching by activity code, city and size shows Ceará companies again.
When the account plan is blocked, the notice's "Go to sign-in" button now ends the session before opening the sign-in page. Before, anyone signing in again came back to the same notice and, after a few tries, got a "too many requests" page.
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.
The desktop register and the phone register print receipts, consumer invoices and labels on a 58 or 80 mm Bluetooth thermal printer, as well as on the cabled printer. Without a printer, the receipt goes to the customer by WhatsApp or SMS.
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.
The Store credit button charges in installments within the customer's limit, and the register warns before charging when the sale exceeds what is available. Customer store credit shows the installments, the overdue ones and the WhatsApp collection with the store's Pix.
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.
On the garment owner's Today: how much I sold today, how much I have in cash, how much I owe the workshops and how many orders are waiting for fabric, each number leading to the screen that adds it up. Three buttons: Sell, See my stores and Ask Tenkai. The salesperson sees her target, the catalog and WhatsApp; whoever only operates the register goes straight to the Phone register.
With the Federal Revenue base loaded, the company tax ID instantly fills in legal name, trade name, activity, city and status, in sign-up, in the partner's invitation and in the register's quick registration. In the garment maker's Welcome, five steps: tax ID, confirm, regime and state, certificate and register invoice code, and the first piece from a photo, with the importer from the previous system alongside.
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.
Simples and micro-entrepreneurs start carrying IBS and CBS on the invoice from 01/04/2027. Tenka already builds that group in its own invoice, the date is in the obligations calendar and in December each Simples company gets the notice, in the reader's language.
Ceará discontinued MFE and the consumer invoice (NFC-e) has been the rule since 01/01/2026. Registers configured with MFE switched to NFC-e by themselves, and the option no longer appears.
In the integration with the network's system, "Clear pending items" immediately closes those for invalid e-mail, partner with no role and inactive account balance, and says how many. Pending items of these three rules are no longer created in any read; the run summary keeps counting how many were ignored.
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.
Asset rental and the rented equipment fleet moved out of Supply Chain and are now in the Rental and fleet group. Anyone who already used them keeps the same access; apparel companies and family accounts no longer see what is not part of their operation.
Household budget, goals, assets, income tax, stock trades, well-being and the monthly conversation are now all in the Family group of the menu. What the household has already entered stays the same; it is just easier to find.
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.
The Verticals screen now has, at the top, the tree of your operation: your company’s verticals and the neighbouring ones you can request, without what has nothing to do with you. Pick one and see, module by module, whether it already works in Tenka, works by connecting to your system or is coming soon in your country. The Request this button registers the request and confirms it right away. The cards for every module are still right below.
The Map by vertical opens on Your operation, the sum of your company’s verticals; picking a parent vertical shows the sum of its children. When the vertical has a chain, the band with its links appears at the top. Each area shows its status in your country: with screens when it already works in Tenka, with the connector when it works by connecting to your system, and dashed with Request this when it is coming soon. Old map links still work.
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.
No text is smaller than 11 px anymore, and the overly light greys in labels and on the sign-in screen are darker. The colored top bar now keeps the search and the View data from selector readable with any company color.
On the phone, the top of the screen now has the menu and title on one line and the buttons on the other. Help and your photo no longer go off screen, the company selector becomes an icon and notifications show as a dot on the bell.
Tenkai answers no longer show internal system names. The source of each figure is now a button with the screen name that opens the already-filtered list in another tab, and the notice for answers without AI wording fits on one line.
In Month cash, overdue items now have their own group, oldest first, with how many days late each one is. Falls due this week shows only what is due in the next seven days, and the overdue totals each have their own line.
On the home dashboard, each revenue and margin figure now states its basis: what was entered this month and is still open, revenue and margin by accrual date, and the income statement net margin in the alert. This makes it clear why two similar figures can differ.
Tenkai no longer uses a fixed lilac: highlights, the answer badge and the circle around its face follow your company color, in light and dark themes.
On record screens, long names wrap onto up to two lines instead of being cut off. While you have not changed any field, Save stays light and No changes yet appears next to it; once you change a field, it lights up.
When the contribution margin shows 100% because no cost is classified as variable, the income statement now says so and takes you to Financial categories to mark the costs that grow with sales. The Account column stays fixed while you scroll through the months.
The Help Center home has a single blue band, with search and "I…" together; clicking the search box no longer makes it look like an error; the Tenkai example sits next to the first steps, with an "Ask my question" button; the partner portal card says you need to sign in as a partner. "What is Tenka" describes today's product (your operation on the industry map, the three situations and the guide per industry) and the status page got the same header and footer as the Help Center.
The Year in review became a dashboard: six indicators (gross and net revenue, costs and expenses, EBITDA, result and margin) with the change over the same period of the previous year, the year month by month in a chart and a table, and the result line by line. Every number leads to the screen it came from: on lines with entries, the click opens the month’s detail. Customers, recurring revenue and digital employees got their own section, separate from the money.
On some screens — the sign-in page, deadline notices, attention cards and the tour dialog — the supporting text and the background of notices were stuck with the light theme color. Now they follow the dark theme and your company color, like the rest of the screen.
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.
The group units screen explains that units only group companies in reports. If you have one or two companies and do not consolidate, you can skip this setup step.
Access denied by group or plan reaches the account administrators as an alert, with the person, the screen, the reason and a shortcut to their access. And Tenkai answers what went wrong today for the people in the account.
Help Center, in the "?" at the top, and Open in the Help Center, in the screen help, take you to the article of the screen you are on. Duplicate articles for a list and its detail screen became one.
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.
In Price lists › Promotions there is the Combo rule: choose the items that go together and the combo price, and the register gives the discount by itself when all of them are in the cart. In the POS, Scale load (Toledo MGV) downloads the file that the Toledo scale software imports, with the price of each item sold by weight.
The policy for when the agent must ask now also applies to requests made to Tenkai on WhatsApp, Teams and chat: a task marked as human or strategic is sent to the screen, and one assigned to a person only goes ahead with them. And the confirmation request shows the before and after of what will change.
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.
When an answer brings many phone numbers, tax IDs or e-mails at once, Tenkai shows only the end of each one in any kind of answer, not only the written ones. Whoever can open the customer register still sees everything.
A synonym approved in Tenkai curation now goes into your company's glossary and changes only your answers — before, it could change the screen search for everyone. Revoking removes the synonym from the glossary.
In the By answer list of Tenkai Usage, each answer now tells which AI model wrote it, next to the queries and the time — or “no AI” when it came straight from the database.
In Tenkai on mobile, each answer now shows the same badge as on the computer: whether it is the data itself, an answer built on proven facts or a question nobody has checked yet.
When you ask Tenkai for each item’s share of the total (for example, "sales by store as a donut"), the answer shows each store with a bar for its share and the percentage beside it, as on the dashboard. If any value is negative, the answer shows largest to smallest, because a pie with a negative slice makes no sense.
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.
In Tenkai Evaluation, "Compare with another model" runs the same cases on the current model and on the chosen one and shows accuracy, consistency, latency and refusals side by side, with the difference between them. The screen tells you beforehand how many calls will be made. Without the AI key set up, the comparison says it was skipped and nothing is spent. Switching is still your decision.
The model card downloaded as PDF or JSON in the Transparency Center now includes the AI provider and model that answer for the company and that model’s latest evaluation (accuracy, consistency and latency). A model not yet evaluated appears as "not yet measured", never as zero.
The Monthly closing screen lists what is pending for the period — unreconciled statement lines, invoices without a fiscal note, notes without an invoice, accruals, accounts that differ from the statement and filings — and each line opens the list that fixes it. Closing with open items asks for a written reservation; reopening asks for the reason. Everything stays in the closing trail.
In Cash forecast, the Likely × chance option uses the date each customer usually pays and weighs the amount by their chance of paying (measured over the last 12 months). The screen says how many inflows were weighted and how much was left out.
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.
Customer subscriptions (Monthly fee tab) now generate the revenue schedule like contracts. In the Accountant cockpit, the deferred revenue report opens by contract and subscription, with recognized, deferred up to 12 months and beyond 12 months. Changed the amount or the end date? Future periods are redone on their own.
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 IBS/CBS impact by NCM, customer and supplier (with the smaller credit from Simples suppliers) now shows year by year, from 2026 to 2033, by the registered reform schedule or, without it, by the law’s calendar. The table exports from the gear.
The name of each vertical and each operation format now follows the language chosen at the top: in the showcase, the map by vertical, account creation and Tenkai. Before, outside Portuguese, the names showed in Portuguese.
Cutting, sewing, piece price, multi-skilling and composition label screens now live under Apparel manufacturing, and collection, trends and collection plan screens under Fashion design — before, everything sat in Supplies, next to stock and purchasing. Whoever used them keeps seeing the same screens, on the same plan.
Each module of the implementation guide now has a step for each of its work screens, with the menu path, what to register first, who does it and how long it takes. The Family, Privacy, Capital, Growth and Network, Business Simulation, Rental and fleet, Apparel manufacturing and Fashion design modules got their own steps.
In the Official loads correspondence queue, the Confirm the ones shown button confirms the filtered list at once, each with the type on its row. The screen also shows each source's description language, and long NCM descriptions now come in full.
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.
My day on the phone shows the daily queue: how many items only you can resolve, how many are late and the first five, each with a shortcut to open it. It is the same queue as on the computer, in the same order.
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.
The platform integrations radar now lists the certifications in the agreed order — production invoices, card terminal, tax receipt, time clock and health insurer — each with what the product already does, what the data confirms and what still depends on outside parties.
DDA slips that matched no bill show up in Post by document. One click builds the proposal with the amount and due date from the barcode, and Confirm saves it under your approval limit. A slip already posted never becomes a duplicate bill.
In Integrations, Test now checks the service invoice token at PlugNotas and sends a test email from your domain to your login, with no need to open each settings screen.
In the dashboard form, when you pick a named metric, you can now write its definition, choose its owner and set a review date. Tenkai only quotes a metric that has a definition and an owner — and now there is a place to fill them in.
The nightly export to your company's storage now writes one Parquet file per subject, each column in its proper type — Power BI, Fabric, BigQuery and Databricks read it directly. If you prefer the previous compressed CSV, choose it in the parameter Warehouse: file format.
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 item Passport tab, the footprint shows as Verified when the fabric supplier provided the batch factor, or Estimated when it uses the average. Each link shows the document that proves the origin: the fabric inbound invoice, the cutting order and the subcontracting shipment. Register the batch factor in the same tab. The public page shows the same in the language of whoever scans the QR.
In Load × capacity, link each machine to a cell: a cell with fewer machines than people is now measured by its machines. Add articles to each machine queue and register the setup minutes per article; the bottleneck adds the setup of each changeover and shows the week load.
In the production order stages table, each stage shows the expected hours from the routing standard time and the variance of what was reported. The stage that went over the expected time turns red. Without a standard time in the routing, a dash is shown.
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.
In the Development tab of the technical sheet, the materials library asks for the supplier of the current cost, and the sample approval asks for the customer who will approve before generating the link.
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.
In the IFRS statement, what one group company has to receive from another, and the other has to pay, is removed from consolidated current assets and liabilities. Only the part that matches on both sides is removed; the difference shows as a mismatch, so you can chase the missing entry. The detail by pair is in the working papers.
Sent the bill or invoice without saying the category? If that issuer already has confirmed entries in this company, the proposal comes with the usual category and supplier, marked with where they came from (for example, 8 of 10 entries). You check and confirm — nothing is posted on its own.
Anyone registered, hired or moved to a new role is enrolled at once in the mandatory tracks that apply to them, with no one having to open the tracks screen.
Exporting the same list again and again now counts as a sign of a side spreadsheet: the Academy and the administrator's summary suggest the dashboard, alert or agent that does it on its own.
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.
The Tenka showcase cards now include a picture of a screen from each module, in the light or dark theme, so you can see it before opening it.
In a demo with a personal link, each topic and each stop of the guided tour enter the link's trail, along with the screens opened.
On lists, the count cards above the table became a strip of counters: the number and the name side by side, and each one still filters when clicked. In Requests and Tickets, Mine, Unassigned and Overdue became ready-made tabs in the views row, next to All; the other shortcuts (no sprint, waiting for client, paused, billable and non-billable) are under Show filters. The filter bar, code, sorting, selection and paging stay as before.
The header of record pages now has three rows. The first has the record code, the Find search and paging, followed by the usual buttons (Favorite to Save). The second shows only the record name. The third is the summary, if you want it: in the gear (Quick settings) you choose the summary fields, the form columns and which tabs stay in the row; the others go to More. More settings opens the full field preferences. The form starts higher up.
Above the pipeline columns there is a thin strip with Win and Lose. Drag the card onto it: Win creates the contract, Lose asks for the reason. While you drag, the strip grows and gets color. Each card shows only the title, the value, a warning when it is an exception and one action (Next action); the rest is under the three-dot button (Win, Lose, follow-up and Edit). When almost the whole column has no next action, the warning shows once at the top of the column. Columns are white and stages scroll sideways.
Month cash and Pipeline now have the Analyze with Tenkai button in the header, like the other result screens. On Month cash, Tenkai reads how the month closes, what is overdue and what to do this week. On Pipeline, the full view (how much is under negotiation, how many opportunities have no next action and which stage holds the money) appears only when you ask.
The footer is now light, with a touch of your company's color, and What's new and Plan appear with a light outline. On the phone, the top bar uses the same icons as the computer: help gets the red dot when there is news, just like on the computer, and the list of news stays on the phone's Home.
The home screen is called "Today" and shows the same data in half the scrolling. At the top, the greeting and the account health; right below, four cards with the result and a small bar for each number: this month's margin next to last month's, what you have to receive with the age of the invoices, your overdue items (for example, 24 of 34) and billing with active clients, contracts about to expire and contracts without adjustment. The operation counters sit on one strip; wins, next actions and radar appear side by side; your start and quick actions become one row of shortcuts; recent activity and maturity close the page. Each block is explained in the "i" icon.
The ring at the top no longer shows 100% when this month's margin is negative. The score starts at 100 and loses points in three pillars: operations (critical requests, quotes waiting for approval, hours that never become an invoice), money (negative margin and how much of what you have to receive is overdue) and deadlines (items in your name past their due date). Next to the ring, a bar for each pillar shows where the loss came from. People who cannot see values get a score without the money pillar.
The sign-in page now fills the whole window, with no frame. The story side has a plain background with the Tenka T behind it, each chapter card sits straight and the cookie notice fits on one line without covering the footer. Under the logo is the motto "Everything's here. And it all connects.", and the first chapter reads "The platform for those who sell work."
The Tenkai panel now shows New conversation, Question library, History and the three-dot button. Inside it, the other tools appear with their names, in three groups: Conversation (analyze this screen, what counts in this conversation, calculation details and clear), View (enlarge and full screen) and Settings (screen knowledge base, my answer style, Ctrl+J and Ctrl+K shortcuts and the AI key). Mode, attachment, audio and voice conversation stay where they were.
On the management P&L, the controls at the top sit on a shorter row, and Excel and PDF are now icons (the name shows on hover). In the table, the currency symbol moved to each column header, zero shows as a dash (the exported spreadsheet still has 0.00) and values no longer have the dotted underline: clicking still opens the entries behind each cell.
The sentences on Today say what something is and where to go, with no exclamation marks and no catchphrases. For example, "All caught up. No urgent action." and "No critical alerts in operations.". Each block's explanation sits in the "i" icon instead of a line under the title.
Lists open with the columns that fit on the screen, with no sideways scrolling on a regular monitor. The other columns stay in Columns, one click away, and are still exported. In Requests and Tickets, the SLA shows as a colored badge: green on time, yellow attention and red overdue.
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 "Get to know this screen" tour points to the blocks of the new dashboard: the account health, the month's four results, the counter strip, the attention blocks and the request charts, in every language.
In the implementation guide, the Profitability simulator step again says what to check: the quick simulation of a contract's real hourly cost and margin, before signing. The text was cut off.
A problem that continues the next day stays in the same open ticket instead of creating another. The daily notice carries only what is urgent or important; the rest goes into the weekly report, with what broke, what got slow and what users could not find, summarized by Tenkai when there is an AI key. The operator also now notices when the same screen is denied to several people and when someone's AI usage goes far beyond normal.
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.
On result screens with the Analyze with Tenkai button (such as the Sales funnel and the Month's cash), when Tenkai is off, has no key or does not answer, the screen shows the numbers it would send, with the notice below, instead of just the notice. And the Load and bottleneck and Integrations radar screens, when empty, say what to do to see something.
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.
The Tenkai question box now shows three lines. A long question fits without scrolling, and the send button stays in the same place.
On the sign-in screen, "Remember my email" and "Forgot password" sit side by side, and the line about what your company did while you were away is back above the form.
The Today panel now has Health of your areas: one light per area you can open — requests, receivables, margin, contracts, strategy, predictability, what is in your name, automatic routines, notices to other systems, Watch and links to other systems —, the worst first, each with a shortcut to its screen. Account health is now the average of these areas, and the bars show the three that weighed most. Instead of the long list of shortcuts at the end of the page, there is one door to each of your modules; every screen is still in the menu and in search (Ctrl+K). Nothing the panel showed was removed.
Menu, screen name, Analyze with Tenkai and the actions (search, Tenkai, notices, help and you) now sit on a single line on the phone, leaving more screen for work. The knowledge base is still in the menu and in search.
In the pipeline closing strip, Lose now has a light red from the start, next to the green of Win: you can see where to drop before you start dragging.
On any record page, More settings (at the bottom of the gear) now gathers everything: drag fields to change the order, a preview of 1, 2 or 3 columns, the tag that says whether a field comes from the system or the company (with a filter), the Fields without a tab group, create tab and move field, and shortcuts to what applies to the whole company. The gear remains a shortcut for columns, summary and tabs in the row.
In More settings on any record page, Tab order lets you drag the tabs, or use the arrows, and the tab row follows that order, only for you and only on that screen.
The record page now has a one-line header (code, Find, paging and the actions up to Save), the summary in one strip and the tabs in one line with More. Lists show counters with the number on top and attachments written on the row. Today opens with your greeting and the day's results; Monthly cash groups what is overdue and what is due this week; Pipeline, P&L and sign-in are more direct; Tenkai has New and History at the top; and the phone shows your day in three numbers.
When an account's dedicated database falls behind the update, the Control Room shows its version and the platform version in red, and Account databases says what is missing. People in that database see scheduled maintenance until the update goes through, instead of opening Access or the owner's dashboard and getting an error.
If a save failed halfway (for example, when changing the theme or the language), the next action on the same screen could fail with an unrelated error. Now whatever was not completed is undone right away and you keep working normally.
The Today panel's account health now also answers in Tenkai — ask "how is my account health?" and it gives the score, the status and the areas that weighed most, with a shortcut to each one's screen. In the BI panel, the Account health (Today) source puts the same score in a card. It is the same number in all three places, counting only the areas you can open.
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.
At the top of the Tenkai chat, next to the name, you see which model answered your last question. A simple question may go to a faster model and a long text to a stronger one: now you can see which it was.
When a sale cannot reduce stock because the register does not know which warehouse the goods leave from, the notice now says where to choose it — Settings › Advanced › Parameters, Operations group — instead of quoting an internal code. The same goes for the sale's financial category and the Z reading e-mail.
The lists on the parameters screen show each option's name — "Simulador — treino", "NFC-e pela internet" — instead of the code, and so does the history. Save now always confirms in the corner of the screen how many parameters changed.
In Settings, the Save button on each tab — account data, identity, notifications, billing, tax, AI, e-mail, language and the others — stores only what is on that tab and always shows the result. Before, a field from another part of the screen could block saving with no notice near the button.
The register now takes stock out of exactly the warehouse chosen in “Warehouse the POS moves”. Before, when one warehouse's internal number matched another warehouse's code, the goods could leave the wrong warehouse.
The POS help and the retail and supermarket setup steps show each field's name as it appears on screen and the path Settings › Advanced › Parameters, instead of internal codes.
When you opened a conversation from the Conversations list, the screen stopped after the customer's name: no messages, no reply box and no Send. Now it shows the whole conversation, each message on the side of whoever wrote it, and the reply you send appears right away. Back takes you to the list.
On the parameters screen, the subgroups that showed the internal name in capitals now have a real name in your language, and the history shows the parameter name translated too. When you save, the notice appears right after the click and stays on screen long enough to be read.
In the Help Center implementation guide in another language, the steps were already translated, but the title of each section — the country, the operation format, each module and your industry — was still in Portuguese. Now the index, the sections and the weeks come in the page's language.
On the sign-in page, “Try it — no sign-up needed” now asks which operation you want to see — retail, healthcare, software house, law firm and the others — and opens a sample company of that kind, view only, with months of real activity. The Tenka overview is still the first option.
In Settings › Subscription you see how much you have used of users, companies, space and API calls per day. At 80% the bar warns; at the limit the new record is refused saying which quota ran out — never again "no permission" without an explanation.
Every week the platform keeps a full, signed export of your account and can generate one on request. If one day you ask to leave, you have 30 days to change your mind; after that, the deletion anonymizes the personal data that must remain and erases the rest, with a trail of what was done.
Every 15 minutes the platform checks for repeated errors on a screen, screens above the agreed time, screens that had data and opened empty, delayed background routines, stuck e-mail or WhatsApp queues, searches with no result, Tenkai's "I couldn't find", abandoned forms, repeated clicks and help that did not help — groups by cause, grades severity by effect and opens the ticket for the Tenka team with "how to reproduce". You see the notice in Tenkai Surveillance marked "(operador)" and, when it is yours, the "Open the ticket" action. Born switched off; switched on first in demo accounts.
Server, database, e-mail and WhatsApp queues, background routines, screen time and the site certificate now have warning and alert limits. On red, whoever is on call is called right away by e-mail and WhatsApp; if nobody confirms within 15 minutes, a second contact is called. During the agreed update window, alerts stay silent. Operations follows everything on a wall panel that refreshes by itself.
Besides application, database and queue, the public status page now shows screen time against the 1.5-second commitment, e-mail delivery, WhatsApp delivery and integrations, each with its current state and the bar of the last 90 days. The numbers are measured by the platform itself every 5 minutes, the same ones the team follows.
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.
Home is now the only way in, with the "Your Home" strip for your role; My week, What I answer for, Inbox and the other start screens became cards in that strip, with nothing lost. And the assistants with people's names became channels of the same Tenkai — "Tenkai · Collections", "Tenkai · Watch" —, each with its own alert choice.
Home, customers, entries, reconciliation, income statement, cash flow, contracts, proposals, CRM, access and the other first-use screens now fit the phone screen: the search takes the full width, buttons are finger-sized and wide tables scroll inside their own box, without pushing the page sideways.
The "What you are responsible for" card on Home now counts your pending items at once instead of fetching one list per subject: the page finishes loading sooner. The full list is still under "See what is mine".
On the mobile Home, the "What Tenkai already knows today" card now uses your company's color, like the rest of the app, instead of the factory blue.
Notices to customers, leads, partners and suppliers (portal, e-mail, WhatsApp, phone) now go through the same door as team notices: they respect the record and the unsubscribe, and each person gets at most 5 automatic notices a day, adding up every routine. Charges, reports, proposals and documents sent on the spot always go out. Ask Tenkai "did the customer get the notice?" to see what happened.
On the Account lifecycle screen, full export and deletion requests go into a queue and run in the background: the list shows the status and the table being processed, without the screen hanging. A deleted account's final package leaves storage after the retention period, and its weekly exports leave right away.
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.
In the SOC 2 auditor package, the Recalculate button now collects the evidence on the spot (if the last one is more than 10 minutes old) — before, it only re-read the last collection and "Collected on" stood still. The daily collection now counts from the age of the last one: restarting the server does not skip a day.
The My preferences screen no longer looks up your language dozens of times every time it opens — now it is once — and stopped logging an error warning on each read when you never chose a language.
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.
The tables inside screens that still had no preferences — subscription invoices and seats, companies, Tenkai credit statement, notifications, item units and variations, knitting and dyeing dashboards, portal orders, learning-path report — now have the gear: choose and order the columns, the rows and the density, and the system remembers it in your account.
The contracts list no longer builds its dashboard twice on every opening, and My preferences reads the settings in one go. Every screen also got lighter: the new request form and the list of colleagues to share a Tenkai answer with only load when you open them. What each screen shows stays the same.
What you choose in a list's gear — hidden columns, order and compact mode — now holds when you come back to the list, reload the page or sign in again, in every list. Before, Customers, Tickets and other lists showed the column you had hidden again.
The Help Center home is now about one tenth of what it was: the search with Tenkai, "I…" to go to what fits you, the first steps, guides by topic with a quick filter, portals, news of the version and of the world, and industries, integrations and plans for those getting to know Tenka. The full catalog moved to "All screens by topic".
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.
Newly released screens show the "In testing" badge until the team validates them on screen; when the badge disappears, the screen has been checked end to end.
An action taken by a digital employee can be undone within the account's window (7 days by default), and the agent only gains autonomy when the rate of proposals accepted untouched supports the scale.
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.
The collection message carries the Pix copy-and-paste code, and the payment received settles the bill on its own. Reconciliation learns from the matches you confirm.
The customer record shows the Tenka score with a sentence explaining why, and Surveillance warns when the score worsens.
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.
Page size, density and the column widths you dragged are saved in your account. Almost 500 tables gained the preferences gear, and rare row actions moved to the ⋯ menu.
When the AI cannot interpret the request and the Builder falls back to keyword reading, the warning now states the cause: timeout, provider refusal or an answer outside the format.
In the consolidated P&L check, the mismatch shows by pair of companies and the open balances between them leave the consolidated balance sheet. Ask Tenkai whether intercompany matches.
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.
The foreign trade process calculates import duty, IPI, PIS, COFINS and grossed-up ICMS from the customs value, with the working and AFRMM, and carries everything to product cost at clearance.
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).
Twelve Help Center guides gained a "Going further" section with your industry's new features: split payment, store credit and pre-sale at the retail checkout, court calculation for law firms, skill-based dispatch in the field, webhooks and SDK for software houses, continuous close for accountants and the daily queue for everyone.
When you open an order, a price list, a ticket or any record, the address bar shows a code instead of the record's sequential number. Old links and the ones sent by e-mail still open the right record.
In the top search (Ctrl+K), registration screens appeared twice, once under the module and once under Registrations. Now each screen appears only once.
The prices and plans page now has a link in the footer of the sign-in screen, next to the Help Center, and in the Subscription tab of the company settings, under "Compare all plans and prices".
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.
The company can turn off Tenkai reading over WhatsApp, and there is a cap on messages per person in 24 hours (default 50, adjustable). Above the cap the channel warns and points to Tenka, which has no limit. The same cap applies to Slack and Teams.
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.
When Tenkai's answer is a time series, the bubble draws a real line, like the dashboard does — rankings stay as bars. On the BI dashboard, a "Filter by text" field understands "store Downtown" or "clear" and applies the global filter without opening the filter panel.
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.
Tour 360 now has tours by segment: apparel, textile chain, software house and services, plus the general one. The tour opens in your company's segment, with four stops and the question that kind of company would ask.
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.
Each alert in the bell shows the icon of what happened — ticket, deadline, approval, message — instead of the same bell. You know what it is about before reading.
The home greeting, the loading indicator (ring and symbol) and the menu's "+ New" button now follow the main color set in Company settings — including on hover.
The Tenkai button at the top now toggles: one click opens, another closes, and it stays highlighted while the panel is open. The "Analyze with Tenkai" bar no longer takes a line of its own — it moved to the screen title line, on the right.
In the kanban funnel each card shows the signals (stalled, no next action) and the value on one line, and the win, lose, apply and edit buttons without wrapping. The drag hint became discreet, next to the selector.
Growth Studio › Campaigns gained a status filter, numbers at the top (active, budget, leads, without UTM), a dense full-width table and the record in a dialog. With no campaign, a single action: create the first one.
The record form no longer appears next to the list in the axis menu (e.g. "E-mail campaigns" and "E-mail campaign" side by side). The form opens from the list, as in the other menus.
When opening BI without choosing a dashboard, the available ones appear as a grid of shortcuts — icon, name and description — with the whole card clickable, instead of one strip per line.
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 pricing table no longer shows two free plans (one was the internal validation plan). The free entry is the read-only demo; paid plans have a 30-day trial. Enterprise Premium now appears with its price.
The 106 screens that only explained what they are gained a frequent question — the one people ask in front of the screen, with the answer — and 27 gained the rule of what the system prevents or decides by itself. Shown in the screen's help button and in the Help Center. Other languages arrive through the translation batch.
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".
Every new password needs at least 8 characters, cannot be your e-mail and cannot be a password that has appeared in public breaches — the check happens without your password leaving the platform. It applies to first access, the reset link, "Change my password", the customer portal and contact access. Account administrators can raise the minimum and set an expiry period in Settings › Parameters.
Each plan states how many Tenkai credits it includes per month (Free 50, queries only; Essential 500; Enterprise 3,000) and the price table shows it. When the allowance runs out, you buy a 1,000-credit pack in Settings › AI — the pack price follows the real cost of the previous month and is shown before you confirm. In the Free plan Tenkai answers queries and, when asked for an action, explains how to change plans.
The Tenka showcase and the price table now show, feature by feature, what is already sellable and what still depends on something external (certificate, production account, card terminal, fiscal device) — so you know before you sign. The guided tour no longer stops at a screen whose only subject is a feature still waiting for that piece.
In Settings › What changes and when you see the regulatory changes that apply to your company — tax reform, INSS and income-tax tables, TISS version — with the date, the rule, the official source and whether the date is confirmed or a forecast. Surveillance warns in advance and Tenkai answers "what changes this year?". It is born switched off; administrators turn it on in Parameters.
In Administration › SOC 2 auditor package, the "Automatic collection" section shows the controls the system checks by itself every cycle — audit trail intact, segregation of duties, retention, password policy, isolation between accounts, unused accounts, backup and background jobs — and the date of the last check. The auditor PDF carries the same matrix: dated evidence, assembled by no one by hand.
Screen reader users hear the name of every filter and form field in entries, contracts, customers, reconciliation, access, preferences, Customer 360, cash flow, implementation, the Tenkai council and the chat itself — no more "edit box" without context. In Tenkai, the action to hear the answer also appears via keyboard.
In Settings › What changes and when, each regulatory change shows, for each company in your account, whether it is to do, in progress or done — with the link to the screen that resolves it and the countdown to the deadline. A score tells, by area and by company, how much of the account is already prepared. Tenkai answers "what is left to do at company X" from the same source.
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.
On mobile, a "Menu" button at the top of the screen opens the side menu. Before, there was no way to open it. With the menu open, the "+" button and the "Get to know this screen" prompt move out of the way.
On mobile, the ⓘ help tooltip opens at the bottom of the screen, complete and on top of everything; before, it was cut off at the edge. In Arabic, the tooltip opens inside the form and the "Get to know this screen" prompt is no longer hidden under the "+" button.
Every record list now has view tabs, the Preferences gear (rows per page, wrap lines, striped rows, compact mode and the visible columns, in the order you drag them) and the row actions in a ⋯ pinned to the right, with Duplicate and Open in new tab. Clicking the row opens the record; Ctrl+click opens it in another tab.
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.
The indicators, blocks and sections of Profitability moved into the same list Preferences dialog, in a single place. Each tick shows or hides right away and is saved.
When you type in the quick search (Ctrl+K or the top field), the screen no longer shows the processing notice at every pause or queues searches: one search at a time, always with the latest term.
In My preferences, appearance, language, briefing and daily summary are saved as soon as you change them, with no Save button, and the sections appear as cards side by side.
The Back button opens the actual previous screen, without the browser asking to resubmit the form. With no previous screen in the system, it takes you to Home.
In the account menu, the list of options scrolls inside and Sign out stays visible at the bottom, at any window height.
All ⓘ tooltip explanations next to the standard fields now appear in the language you chose: more than 4 thousand texts, on every screen. In the previous version, only the thousand most used were translated.
When you open a screen from the quick search (Ctrl+K) or the Back button, the loading notice appears the moment you click, instead of the screen looking frozen until the next one starts to arrive.
In Profitability, the list views and the dashboard views (period and indicators) are in the same Views button, each in its own group.
On short screens, such as 14-inch laptops, the screen title, the top of the page and the filter bar take less space, and the list starts higher up.
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.
At the top of Tenkai, the + starts a new conversation without erasing the history, the book opens the library with ready questions for this screen and the usual ones, and the full screen button opens the panel in the whole window. The gear leads to the answer style.
The agent created in the Builder now has a "Run now" button: it works right away, without waiting for the schedule, and the result shows up in the Decision trail. It follows the same rules as the schedule: if agents are turned off on the platform or the agent is paused, it says so and does not run.
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.
In lists, the table takes exactly the space left in the window: the page no longer scrolls along, only the table does, with the header and pinned columns always in view and the paginator right below.
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.
The Help Center home page shows the documentation numbers and four shortcuts (getting started, onboarding guides, what's new and support), and the guides appear as cards by industry, split between the textile chain and other industries.
When you start editing a record and leave without saving, its row is highlighted in amber in the list, with a note that there is an unsaved draft — open it and pick up where you left off. The list no longer offers "we recovered what you typed" without saying which record.
The row actions menu and More actions scroll inside when the options do not fit on the screen; columns sit closer together, so more fits in the same width; and the indicator cards in Demands and Tickets are compact, in two rows, leaving the table in view when you open them.
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.
On a laptop screen the filter bar no longer stacks one field per line: fields run in a row and wrap together. Each screen's own buttons sit on a second line, aligned with the search. In forms, the actions (Back, New, Save) stay together, with search and paging right below.
Tables with several fixed-width columns left the main column (customer, name) with a few pixels, and the text broke letter by letter. Now the table fits its content, the main column has a minimum width and amounts and codes never break — in Vouchers and benefits and 22 other screens.
The Why Tenka page in the Help Center now also compares textile and fashion ERPs, with rows for the textile chain in one system, traceability to the bale, POS, cotton currency, tech pack and investigating the cause of a number — including the rows where we still lose.
The catalog goes back to the base plans: Free, Start, Grow, Enterprise and Enterprise Premium. Your sector's vertical (textile, health, legal, field or family) is an add-on module with its own price, contracted at sign-up and added to the same plan invoice. Existing accounts pay nothing extra.
The section Verticals: add-on modules lists each vertical and how much it adds per month to the plan. The section with apparel plans by size is gone.
The household account now starts on Start with the Family module, and the menu keeps only what a household uses. The employee benefit is the same module, paid by the company.
On the desktop, menu, header and page became three cards that fill the whole screen. Only the page scrolls, inside its own card; the screen title stays still above it and nothing slides under it. The double scroll is gone and the end of the menu is no longer cut off.
The sales rep commission entry, and every vertical entry that had to create the account's first financial category, was failing. The category is now created with the user who registered it.
When generating the textile demo, a table the generator could not fill now shows in the report with the error, instead of staying silently empty.
The catalog now has prices for claude-sonnet-4 and for three free Zen models the panel flagged as unpriced.
The receipt of a paid invoice opens again as a card, with the amount, the billing details and the print and back buttons, on mobile too. The notice for an unpaid invoice shows in the warning color.
In the Subscription tab of the settings, the help panel opens again, and the card payment dialog shows the error inside it without reloading the page. The card fields fit entirely in the dialog.
The monthly "what changed on the platform" email arrives only once for each person. Before, someone who managed several companies got an identical copy per company.
The ⓘ tooltip next to each field, with its explanation and example, now appears in the language you chose. Before, the field name was already translated but the explanation stayed in Portuguese. The most used texts come first; the rest arrive in the next versions.
The Demo Group now has one company per link: cotton gin, spinning mill, knitting mill, dye house, sewing contractor, apparel maker and store, with one year of operation and the invoices between them. Each company has logins by area (administration, finance, HR, design, marketing, sales, sales rep and salesperson) and the customer portal.
In Exchanges, a register sale can now be cancelled in full, with a reason. The receivable is cancelled, the items return to stock and the sale leaves the expected cash. A sale with an authorized consumer invoice (NFC-e) or with an exchange cannot be cancelled here.
In the WhatsApp channel, choose whether the number belongs to the platform or to your own Meta account. Messages through the platform number count toward the plan allowance (500, 2,000 or 10,000 per month) and the excess costs R$ 0.15 each. Messages through your own account are already billed to you by Meta, and Tenka does not count them again.
The invoice now bills the digital employee that ran at least one routine in the month. Hired but idle is not billed. The plan includes some at no cost (Evoluir 1, Enterprise 3, Enterprise Premium 5), shown on the invoice as included in the plan.
In the decision trail, the responsible column shows the person name instead of the user number.
Apparel makers get three plans by size of operation: Ateliê (R$ 297, up to 15 seamstresses and 1 tax ID), Fábrica (R$ 497, up to 60 seamstresses and 2 tax IDs) and Indústria (R$ 897, no seamstress cap and 3 tax IDs). They appear in their own section of the pricing page, and at sign-up for whoever picks the textile industry.
Each anchor partner has its own model: the partner pays the plan of each active account, the member pays with the program discount, or the member pays full price and the partner earns a commission. The panel shows who pays what in the month. Only BMCode changes the model, because it is the contract.
Invalid or duplicate e-mail, a partner that is neither customer nor supplier and has no activity, and the balance of an inactive bank account no longer become issues. Each run summary counts every case, and old issues of these kinds were closed as ignored.
A contact whose e-mail already belongs to another contact no longer breaks contact synchronization in the next run.
Your own API key is no longer replaced by browser autofill. A value that does not look like a key is rejected and the saved key is kept.
Prices for kimi-k2.5 and 24 more Zen models are now in the catalog. When you pick the default model, input and output per 1 million tokens fill in automatically.
A company establishment with more than 60 secondary activity codes (CNAE) no longer interrupts the Federal Revenue base load.
In the platform parameters, the Prospecting group now has a shortcut to the Federal Revenue base load panel.
In the contract list, type the number shown in the column (for example 413) and the contract appears. The number matches whole: 41 does not bring 413. Customer name, status, nature, history and attachments still work in the same box.
In the textile Demo Group, the picking TV and the stock handler's scanner open with orders to pick. After the demo, "Restore example" fills the queue again.
After an update, the Home cards took about 20 seconds to appear on the first open. Now they arrive in about 2 seconds, like the following opens.
When choosing a language for the first time, Home and the service order record could open empty. Now they open normally from the first time.
In the contract list, the views (revenue, expenses, consolidated) and the cockpit shortcut moved to the top of the panel: the search box takes the whole row and the filters button no longer overlaps it.
A field the system requires shows * even when your company customized the screen fields — like the project Type and Name. In the label template, the Field column shows the full name again; and the segregation-of-duties severity and the PDV receipt payment method appear in your language.
In the contract list and other screens with a panel, the list sometimes kept showing the previous search while the indicators had already changed. Now both always show the same set. Also: the "What I decided" column of the Tenkai trail shows again, the agents' office no longer hides an agent without a start time, and session packages and acquirer statement sales no longer offer a Delete that always refused.
In the preview, a row with an invalid e-mail (for example several addresses in one cell) already shows as invalid, with the column and the reason. If saving still fails, the message names the row, the name, the reason and how many rows already went in — instead of "contact support".
Energy, cotton purchasing, yarn cost, spinning maintenance, FX desk, knitting, produced × resold, dyehouse billing, received invoices, warehouse, traceability, workday and NR, skill matrix and pieces per worker: the indicators stay on top and the records come below in the standard list — search, filters, saved views and export.
Serialized units, rental fleet, certifications, resources and capacity and the trend radar became a standard list + form: filters, saved views, export and the trash with Undo. The address of each screen stayed the same.
Production process, collections, collection plan, composition label, foreign trade, subcontracting and work orders open in the standard form, with the details (steps, pieces, lines, fibers, cargo items, returns, logs) in tabs and new items added through a dialog.
Registering an entry, exit, adjustment or transfer now uses the standard form (Save, Save and close, Ctrl+S); the balance still updates in the same step and the current balance shows while you fill it in.
The preview of the composition label now lists the chosen care instructions — before, it never showed them, even when they were selected.
Audit trail, e-mail queue, background jobs, errors, notifications, received webhooks and access log got the standard list: search, filters in the side panel, saved views and Excel/PDF of the whole set. Records are not edited or deleted there — they are the proof of what happened.
For platform administrators: companies, accounts, plans, screens, access groups, users, screen layouts, incidents, legal and trust documents and factory tips moved to the standard list and record — with filters, views, export and the details (versions, permissions, companies and groups, fields) edited in dialogs. Old addresses still open.
The heat map stays on top; below, risks sit in a list with filters by category, level and status, the "Above appetite" column, views, export and a trash with Undo. The risk record carries the plan’s actions and the indicators (KRIs), each edited in a dialog.
Consents sit in a list with the Data Protection Officer (DPO) on top and a Revoke button on each row that records the date. The processing map (ROPA, art. 37) became its own register in the menu, with search, a legal-basis filter, export and a trash with Undo. The old address still opens.
Customer portal users, business partner users and conversations moved to the standard list, with search, filters, views and export. In conversations, "New conversation" and delete stay on the toolbar and the row; in notifications, "Mark all as read" is on the toolbar.
Sales ▸ Online sales channels became a list with search, filters, views, columns, export and a recycle bin with Undo, and each channel opens in a record with its feed, webhook and the orders that came through it. Fetching orders, testing and authorizing Mercado Livre sit in the row ⋮ and at the top of the record.
Sales ▸ Consignment became a dashboard: what is out of the house by type at the top (click narrows the list), filters, views and export. Each shipment opens in a record with the Pieces tab — add pieces and settle each one by dialog, all sold, all returned, term and cancellation as before.
Sales ▸ Sales reps became a list with search, filters, views and export, with the month ranking at the top. Each rep opens in a record with the month indicators and the Target and commission, Portfolio and Visit routes tabs.
Sales ▸ Targets and commissions got the standard list: indicators and the queue of who is below 80% at the top, and the team with target, sold, achievement, tier and expected commission, with role filter, views, columns and export. The statement opens from the row icon.
Sales ▸ Anchor network became a standard record: the brand the portfolio sees and, in tabs, the published catalog (publish and edit by dialog), the orders that came from the network and the onboarding cohorts with their accounts.
Sales ▸ Price lists became a list with search, filters, views, export and recycle bin, with the simulator and promotions at the top. Each list opens in a record with the Item prices tab — prices are now edited by dialog — and repricing from today's cost.
Sales ▸ Contracts got the standard list without losing the dashboard: KPIs by view, queue, quick filter and kanban stay at the top, and below come saved views, the columns you choose, the peek with the contract dossier and export of the whole set — before, Excel stopped at 1,000 rows.
Sales ▸ Contract cockpit became a standard dashboard: the portfolio reading, the consolidated by counterparty with netting and the analyses sit at the top, and below come the contracts of the same cut with search, views and export.
Operations ▸ Log hours got the standard list: KPIs sum the whole period in the database (before, only the 200 most recent entries), the period sits on the filter rail, and there are search, filters by billing, type and approval, views, columns and export. Quick logging stays the same.
Operations ▸ Field measurement became the list of measurement reports, with search, filters, views and export. Generating the report, the visit schedule (new schedule by dialog) and the work order checklist (item by dialog, close the work order) sit at the top of the same screen.
Operations ▸ Shipping center got the standard list: the stage cards narrow the list, the mode becomes a filter, and there are search, views, columns and export of the whole set. The shipment card (dispatch, label, delivery) opens from the row ⋮; route sheets, integrations, calls and lead times stay in the tabs.
Operations ▸ Own fleet became a list with search, filters, views, export and recycle bin with Undo, with maintenance due at the top. Each vehicle opens in a record with the cost per km and the Refuels and Maintenance tabs, logged by dialog.
Operations ▸ Work orders: the record now follows the standard layout. At the top, customer, equipment and contract with the deadline alongside; materials and hours in tabs, added through a dialog; schedule, report and closing on the Schedule and field tab. Save recalculates the deadline, and the record gained previous/next, duplicate, attachments, comments and history.
Operations ▸ Project studio: the idea now opens with the standard header — Save (idea and canvas at once), attachments, comments and history —, the whole studio right below with the conversation and the same tabs, and the Idea record tab for title and problem. Delete archives the idea.
Operations ▸ Projects: the list gained filters, saved views, full-set export and the period cut on the rail, with the draggable board at the top and the milestones-and-tasks drawer from the row action. The record follows the standard: Data tab with justification and risk as text, cycle, summary, EVM and baseline above the tabs, and the rituals in the header ⋮.
Settings ▸ Webhooks got the system list — search, filters, views and export — with the latest deliveries and Send test at the top, and the standard record with the secret (and a button to generate another) and the choice of events.
Settings ▸ API keys got the system list — search, filters, views and export — with issuing, identity readiness and the upsell at the top, Scope and Revoke on the row, and "How to use the API" collapsed. The record edits the name and has Scope and Revoke in the header.
Settings ▸ Tracks got the system list — search, filters, views and export — with what each track does today and since when. The record edits the behaviour, publishes a new version on each Save and shows the version history in a tab; exclusive companies have their own tab.
Settings ▸ Object studio got the system list — search, filters, views, export and trash with Undo — with how many fields and records each record type has. The record has name and description on the Data tab and the fields on the Fields tab; a new record type can start from a spreadsheet, with a preview before creating.
Settings ▸ Automations got the system list — search, filters, views, export and trash with Undo — with the gallery, waits and latest executions at the top and on/off on the row. The record has the trigger and its setup on the Data tab, conditions and actions in tabs, and the dry-run in the header. Tenkai’s draft opens straight on the record.
Settings ▸ Tenkai context became a panel: knowledge items in the system list — search, filters, views and export — and in a record with the content; at the top, the usage of the limits and, collapsed, the preview, capabilities, external sources, usage log and verified answers.
Settings ▸ Groups and access got the system list for groups — search, views, columns and export — with people and links at the top, and a record for each group with the Screens and permissions (one click per verb, saved immediately), BI panels and Restricted to the group tabs. The usual locks remain.
Finance ▸ Financial approvals got the system list — search, filters, views and export, opening on pending — and a record for each approval with the Decide button in the header. The e-mail link opens the record directly.
Finance ▸ Partner balance got the system list for the statement — search, filters by partner, type and origin, views and export — with each partner’s balance at the top and debit and commission from the bar.
Finance ▸ Acquirer reconciliation got the system list for statement sales — search, filters, views and export — with the indicators at the top (click to narrow) and the CSV import right below. The divergent-fee alert now opens the list on the divergent ones.
Finance ▸ Center structure now lives in the profit centers list: the tree sits in a collapsible block at the top, with move, make root, visibility and type on each node, and CAPEX, allocation and tree import on the bar — together with the list’s search, filters and export.
Finance ▸ Connected accounts got the system list — search, filters, views and export — with the consent warnings at the top, Sync and Revoke on each row, and Link connection in its own record that searches the item’s accounts for you to choose.
Finance ▸ Flow by nature got, below the matrix, the system list with the bills due in the month — search, filters by nature, center and status, views and export — and each row opens the transaction record. Changing the month in the matrix updates both.
Finance ▸ Profitability now uses the system list for contracts — search, views, columns and export — with the profitability filters in the filter panel and the analysis, cards and sections by customer, partner, project and employee at the top. Each contract opens its record.
Your account’s datasets got the standard list (search, filters, saved views, export) and the standard form: source, fields and name in one place, and Save stores the dataset with its fields at once. Delete deactivates — panels already using the dataset keep working.
The BI panel builder got the header and shortcuts of the other forms — Save (Ctrl+S), Save and close, Duplicate, move between panels — and the layout, filters and history became tabs. Delete sends the panel to the trash, with Undo.
Partners’ OEM profiles got the standard list (search, filters, saved views, export) and the standard form, with a unique partner code per profile. Linking a tenant to the partner stays at the top of the list; delete deactivates the profile.
A/B tests got the standard list (search, filters, saved views, export and trash with Undo) and the standard form. The power calculation sits in the form header, and the sequential test runs from the form or from each row’s ⋮.
The group chain cockpit keeps the per-link numbers and the transfers on top and gained, below, the standard list of links — each company selected at the top with input, output, yield, revenue, cost and margin — with search, columns, saved views and export.
The file connector keeps the upload and the batch review on top and gained, below, the standard list of imported batches — with search, filter by record type and status, views and export. Any old batch reopens in the review from the row’s ⋮.
The chart of accounts got the standard list (search, filters by type, nature and Fleuriet class, views and export) and the standard form to adjust an account. "Make it the company chart" stays on the list bar, and accounts with entries remain protected.
E-mail campaigns got the standard list (search, filters by audience and status, views, export and trash) and the standard form, with the "List and send" tab: build the list, send a test, launch and see each recipient.
The tender radar keeps the figures and "Collect now" on top and shows tenders in the standard list (search, filters by status and state, views, export), with turn into opportunity and discard in each row’s ⋮. The criteria got their own list and form, with trash.
The technographic radar keeps the gate, the scan and the per-product cards on top and shows signal leads in the standard list (search, filters by status and state, views, export), with import, enrich and discard in each row’s ⋮. Products and signals got their own list and form, with the Tenkai suggestion.
Booking links got the standard list (search, filters by host and format, views, export and trash) and the standard form, with the "Link and preview" and "Booked meetings" tabs. Meetings from all links stay at the top of the list, with cancel.
The ICP keeps the portrait, the axes and the calculation memo on top and shows the ranking of scored leads in the standard list — best fit first, with search, columns, saved views and export of the whole set. The lead’s name opens its form.
The proposal opens in the standard form — Save (Ctrl+S), Save and close, move between proposals, history — with the items on their own tab, edited through the dialog. The 3-option mode, value-based pricing, sending, new version and signature stay where you look for them.
The record types your company creates in the Object Studio got the standard list — search in the content, columns, views, export of the whole set and trash with Undo — and the standard form, with the object’s fields and Save (Ctrl+S).
External factors got the standard list — search, category filter, views, export and trash with Undo — with urgency and balance on top, and the standard form. "Send to SWOT" is in the row’s ⋮ and in the form header.
Information topics got the standard list, sorted by the largest gap, with blind spots on top; key questions got their own list and form, with the question-of-the-day rotation in the row’s ⋮.
The indicator cockpit got the standard header — arrows and search between indicators, activity trail, Delete with trash — and the follow-up in tabs: series and calculation, calculation run, FCA and actions (new action in a dialog) and Tenkai analyses.
Saved reports got the standard list (search, columns, views, export and trash with Undo) and the standard form, with name and schedule on top and the builder on the Build tab. Before, saving a reopened report created a copy; now it saves the report itself, and copying is Duplicate.
Segments got the standard list (search, columns, views, export and trash with Undo) and the standard form; the growth × margin matrix and the customers still without a segment remain above the list.
The period’s schedule got the standard list — search, columns, views and export — with View and Generate the period on top and transmit and mark as paid in the row’s ⋮. Electronic powers of attorney got their own list and form, with the validity coloured (expired or expiring within 30 days).
Document management got the standard list — the four numbers on top, search, category and status filters, views, export and trash with Undo — and the standard form, with the Versions tab and Archive in the header. Global search (F4) opens the document straight in its form.
Tenkai’s scheduled questions got the standard list — only yours, with the three numbers on top and send now and on/off in the row’s ⋮ — and the standard form. Delete now goes to the trash, with Undo.
Policies got the standard list (search, subject filter, views, export and trash with Undo) and the standard form, with the Versions, Clauses and Simulate tabs. A new policy is still born with version 1 in force.
Agent designs got the standard list (search, columns, views, export and trash with Undo) and the builder moved to the standard form, with the steps in tabs: request, powers, rehearsal and versions. A design that already created an agent does not go to the trash.
Cases got the standard list — client, open deadlines and next deadline per row, filters, views, export and trash with Undo, close in the ⋮ — and the standard case form, with finance, work, progress, parties and documents in tabs.
The board got the standard list — only open deadlines, by date, with the band coloured, "only mine" on top and fulfil/cancel in the ⋮ with the reason in a dialog — and the standard deadline form, with the hearing time.
Payroll periods got the standard list (open and accrue on top) and the standard month form, with employees in a tab, events and the contractor’s invoice in the usual dialog, and close/reopen, partner and eSocial in the header.
Profit-sharing programs got the standard list and the standard form, with the goal basket and participants in tabs (added through a dialog) and the calculation — accrue in the P&L and pay through payroll — in the last tab.
Time entries got the standard list, filtered by employee and month with the month’s numbers on top, and the standard day form with the four punches — hours are still calculated from the schedule.
Wiki pages got the standard list (search in content, views, export and trash with Undo, "New SOP" in the bar) and the standard form, with markdown and preview side by side and the Versions tab.
The root-cause investigation got the standard header, with the problem always in view and the why-tree, the 5W2H plan and the investigation’s plans in tabs; Save (Ctrl+S) stores the plan with its lines.
Session packages got the standard list — balance per row, use and view uses in the ⋮ — and the standard form, with "use session" in the header and the Uses tab.
In the SAML, OAuth, MCP, sandbox and sensitive-field settings, in diagnostics, batch translation and the account view, section titles now have the same size and colour as the rest of the platform, in both light and dark themes.
The contract form, the requests kanban, the squad room in TV mode, resources, performance review, the operations cockpit and the printed POS packing slip now follow the single platform look: they look the same as before, and the dark theme applies equally on these screens.
After an update, the first person to open Home waited more than 20 seconds for the lower cards. Now the system prepares that path on its own right after starting, and the first visit is as fast as the next ones.
On the pipeline board, the "stalled too long" badge no longer touches the opportunity title in dark mode; the spacing is the same in both themes, and the badge wraps to the next line with room when the title is long.
Ask "which fields did we create in Customers?" or "how many customers by Cost center?" and Tenkai answers even when the AI is down. When the field is sensitive, does not exist or has not been created yet, it tells you why instead of "no data found".
In the analytics API and the MCP, without a column list you get only the dataset columns; fields created by the company come when requested by name. A sensitive field follows the screen rule: without "View Values" it is left out and cannot filter or group either.
In quotes, sales orders and inventory counts, the item is edited from the pencil on its row, in a window with all its fields: each supplier's price, the order line with variant, unit, warehouse, lot and price, the payment method and the count by size and color. The grid shows the result and the rules are the same.
Notices, error and validation messages, the Home radar and next actions, the guided plan, form section titles, status options in lists, chart months, due-date ranges and Tenkai's answers now come out in the language you chose — not just the screen labels.
In Rolls, the "Scale and printer on this computer" bar lists the scales the browser has already authorized on this computer, connects the one you pick and remembers it for you. The stable weight goes into the weighing by itself. Toledo continuous, ENQ request (Toledo Prix, Filizola, Urano), generic or your own expression, with adjustable speed and parity. Works in Chrome and Edge; in other browsers the screen says why and the weight is typed as before.
When you close the rolls, the label prints on the printer you chose: straight to Zebra and compatibles (ZPL) over USB or serial, or through the print dialog at the exact label size, on any printer. If direct sending fails, the print dialog opens by itself — the label is never lost. Your choice is remembered.
When weighing, choose the production order: the item, production lot and warehouse come from it, and the roll inherits the lot. The roll list filters by order, and Tenkai answers "how many rolls in order 345?".
In the item record, the "Lot-controlled" option makes the lot required on the roll, on the production order and on shipments to third parties. With a production order, the lot comes from the order. Sales and dispatch, which don’t ask for a lot, stay the same.
The roll list gained the Company, Order and Item columns and the Reprint label and Cancel actions. Cancel asks for a reason and deletes nothing: the roll stays cancelled, out of the balance, with who cancelled it and when. Ask Tenkai "which rolls were cancelled?".
New screen Supplies → Label templates: size in millimetres, printer resolution, QR or barcode, and the fields (item, colour, lot, dye batch, order, weight, length, location, company, date) in the order and font size you want, with an actual-size preview and "Print test". Mark one as the company default: it is what the rolls screen uses.
Sending a collection plan or a screen layout to the trash no longer deletes it for good: it goes to the trash, with Undo, and comes back with everything it had. When deleting is refused (a collection that already created stock items, a published agent), the reason shows in the notice next to where you clicked.
The foreign trade process record, a new outsourced processing shipment, the dataset and the BI dashboard builder open again. The line windows of the collection plan, collection colors and pieces, foreign trade steps and items, processing return, fleet rental and billing dispute now save what you typed. And Save turns on as soon as you change any field of the record.
In dozens of lists the search box filtered nothing. Now every list searches by the fields that identify the record — name, description, title, number, code, reference — and, when the main column is another record (the user, the item, the partner), by its name. In versatility, the person’s name also finds the row.
Old bookmarks and links to webhooks, API keys, tracks, object studio, automations, Tenkai context, sales channels, sales reps, price lists, field measurement and fleet open the new screen again instead of "access denied". And the links the system builds itself — deadline alerts, household cash flow, card statement, exchange rate, supplier certifications — open the list already filtered, with the filter warning only when it is real, and just once.
In Rolls, the buttons to connect and authorize the scale and to authorize the printer respond again. With the menu collapsed, the logo sits on top and the expand button below, and the plan icon no longer hides behind the footer. Cotton purchasing, yarn cost and the blend record open much faster: the bale share by grade went from one query per blend to a single one.
The risk list shows category, treatment, status and level in your language (no longer OPERACIONAL, MEDIO, ABERTO), including in the save message. Renamed screens and the knitting, finishing and family modules appear translated in the menu. In dark mode, the contract status strip is no longer a white card, and the label template’s "Field" column no longer disappears.
On the public reporting channel, after Send the screen shows the tracking protocol right away — before, the report was saved but the number did not appear.
In the outsourced processing shipment, the Item combo no longer slides under Warehouse and Lot, and Record return opens on the cost, without the calendar covering the quantity. The Fields tab of the label template fits without scrolling. In lists with many columns, the row actions stay fixed on the right. With the menu collapsed, the plan icon no longer sits under the footer.
The button to finance and the discovery card on Home appear in your language, the work order Nature shows Preventive, Corrective, Emergency and Installation (no longer the code), and table paginators no longer say "(1 of 1)" in English. On the contract, in dark mode, the finance and signature badges and the completed steps are readable again.
In the demo account, the Tenkai decision trail shows complete decisions — when, which agent, what it saw, what it decided, the level, the status and who is responsible — instead of empty rows with "ATIVO".
A company field marked sensitive shows as ••• for anyone without "See Values" in the list, PDF, Excel, CSV and BI — and now it cannot be used as a filter by link nor goes into the automatic draft. Tenkai never receives its value.
In the scenario levers tab, the row pencil opens the same dialog to fix type, value or dates, without removing and recreating. The table shows the lever name in your language, not the code.
Tenkai's decision trail shows the agent name, status and autonomy level in words; the financial entry allocation shows the percentage in your country's format (90.00 %).
In BI ▸ Explore, the fields your company created (cost center, region, owner…) appear in "Group by": how many records and how much they add up to per field value, with the filter applied too.
In the spinning mix, picking a bale that another mix has just reserved now shows a warning and refreshes the list, instead of doing nothing.
The main numbers show up first and the supporting cards (what needs you, checklist, discovery, your role's home, exceptions and the next step) arrive right after, without freezing the screen.
Status labels (Open, Draft, Completed…), on-screen notices, the comparison with the previous month in finance and the closing narrative now come out in the language you chose. We also fixed translated texts that had Portuguese words in the middle.
On more than 150 dashboards and tools, the title repeated inside the page is gone: the screen name stays at the top, the same as in the menu, leaving more room for the content. Exported files now carry the screen name.
The whistleblowing channel now has the standard filter bar: search by protocol or subject, narrow by status and save as a view the cut the committee repeats. The developer sandbox also moved to the standard bar.
In knitting, spinning and apparel, opportunities and the pipeline show "Monthly value" instead of MRR (which belongs to subscription sellers); yarn cost separates the target markup, on cost, from the margin on price; and the collection plan separates the planned line from the piece sold.
In Settings ▸ Company fields, pick the table by its menu name — customers, suppliers, items, contracts, any record you can reach — and create as many fields as you need, with type, description and whether it is required.
The field becomes a column in the table list, a filter in the side panel and goes out in PDF, Excel and CSV exports. The list dashboard adds up only what the filter kept.
In BI Explore, datasets of tables with company fields bring those fields as columns to tick, filter and export.
A company field marked required will not let the form save empty — before, it only showed the asterisk. It also applies when editing an old record.
Three new field types: money (respects "See Values"), long text for notes and a record from another table — for example, choosing the responsible supplier on the customer record.
Mark a field as sensitive: it never goes to Tenkai and shows as ••• in the list, export and BI for anyone without "See Values".
In the form Preferences and the list column gear, each person shows or hides the company fields they do not use. The administrator decides whether the field starts in the list.
The Company fields screen did not show under Settings for administrators of accounts created after August. It now follows the Company settings permissions.
Company fields created for Project now show on the project record, in the Data tab — before, they were created and showed nowhere.
Ask "how many customers per cost centre?" or "which fields did we create on the supplier?": Tenkai counts per value and opens the list already filtered. It never reads a sensitive field.
In the P&L, cash flow, statement, live margin, BI Explore and other queries, the filter sits in the standard top bar: what you typed is no longer lost when the screen refreshes.
Management P&L, cash flow, live margin, portfolio, work-order map, rolls, third-party material, personas, vouchers and the Tenkai screens now have saved views: build the cut and reopen it the same way.
Blend bales, investment assets and income, entry allocation, scenario levers, quote items and dispatch lines are now added and edited through a dialog, as on the product record.
Fixes on screens where the typed field was lost: Apply on personas, the decision trail clause, the clinic calendar appointment when changing day, the Tenkai board month and the timeline shortcut.
Lots, contracts, receipts and purchasing now say "cotton lint" — the term of the CEPEA/ESALQ index and of the market. Searching "lint" still finds the screen.
The group’s spinning mill sells to its knitting mill and the knitting mill to its garment maker through the Chain Network: the offer appears inside the customer company, the order comes back as a sale and the invoice lands in its incoming invoices with the lot, the dye lot and each roll with its weight. In the test environment the invoice stays simulated — and only crosses to accounts also in the test environment.
When the fabric is entered in the order, the rib (or cuff, collar) goes in by itself at the article’s or the customer’s percentage, in the same colour, and recalculates when the fabric changes. Matching may require the same dye lot or the same dye house — and picking only offers a roll that matches.
Each roll lives in a location (aisle, rack, shelf, position) with a scannable code. The handheld shows the order queue with the suggested rolls in route order; the picker just scans. Relocating, checking the invoice’s dispatch, transferring to a store and counting by position are on the same handheld — and the location only changes by scanning.
The 10.2 kg rib comes out of roll 12 of 28 kg: the handheld weighs it, 12-A is born inheriting lot, dye lot, colour and location, and 12 goes back with the rest. Cutting loss is declared, and the lot balance does not change.
Dispatch keeps which rolls left on each line, whole or cut, with the weight; the invoice carries the rolls on the item. With the dispatch check on, the invoice is only transmitted after all rolls are scanned. Store transfers leave and arrive by scanning, and any difference becomes an incident.
By article, side by side: the ledger balance, the sum of rolls, what is at the dye house, what left without an invoice and the tax balance. The difference comes explained (unweighed roll, cutting loss, pending invoice, roll in transit) and the month’s reconciliation is saved and signed.
On receipt, the handheld suggests the position by the article’s ABC class, the same dye lot and the weight. The panel shows idle rolls and generates today’s cycle count (A weekly, B monthly, C quarterly). RFID is prepared: the roll accepts the EPC and the portal reader has a way in.
The queue of orders to pick on a warehouse TV, with the roll to take and its location, the rib to cut and the state of each line — each scan on the handheld updates the TV. In the store, the customer follows their order on the TV: received, picking, cutting rib, checked, ready for pickup — with no personal data on screen.
Each person with their own target (value, pieces and kg) and rule: by role, article line or customer, with target tiers, a cut when discounts exceed the approval limit, and validity. Closing keeps a line-by-line statement and the panel shows who is above and below.
Silver, Gold, Diamond by volume over the last 12 months: the tier discount goes into each order line by itself, with its own label, next to the cashback the customer uses as payment. The tier goes up and down at the monthly recalculation, with history.
The mill that imports viscose and linen and resells from stock sees revenue, cost and margin for produced, domestic resale and imported resale side by side. A resale article needs no yarn recipe.
The mill’s showcase with vivid colours and photos per colour. The customer picks the silhouette — T-shirt, trousers, dress — and sees right away how many pieces a kilo yields, the fabric cost per piece at their price and the profit per piece and per kilo at their intended selling price. From the simulator they order, rib matched. Via the public link or inside the portal.
With the A1 certificate, the system fetches from the tax authority every invoice issued to the company’s tax ID — every hour, from where it left off — and puts it in Received invoices. The acknowledgment goes out by itself so the full XML arrives. Nobody asks for the XML by e-mail anymore.
Every invoice issued to the company — from the tax authority, the group network or uploaded XML (one, several or a .zip) — in one place, with the suggested purchase order and the item for each line from the mapping the system learns. Post one or several at once.
Acknowledgment, confirmation, disclaimer and operation not performed, signed with the A1 certificate and sent to the tax authority. The deadline for the final response shows on each invoice, and every event is recorded. Disclaiming protects the company from a fake invoice issued in its name.
From any point — roll, yarn lot, dye lot, bale, shipment, order — the whole tree: backwards to the cotton lint, the contract and the certification; forwards to who received it, with order and invoice. Each node’s complaints show with the decided merit.
Each return’s service invoice comes in with its items and is checked line by line against the third party’s table and what came back: kg, price and reprocessing. Matches become bills; mismatches become disputes that the dye house sees and answers on the portal.
Every returned roll is checked — ΔE, width, weight, shrinkage, defects. Out of range, it goes to quarantine and opens a complaint to the dye house with the trace ready. The scorecard compares dye houses by lead time, RFT, ΔE, loss, billing, complaints and real cost per kg.
An upheld complaint leads, through the timeline, to the dye lot and the yarn lot. With one click every roll still in stock is blocked, the list of who already received appears so you can warn them, and the child complaint opens at the dye house or the group’s spinning mill with the cost passed on.
Select the group’s companies and see the whole chain: how much cotton lint became yarn, how much yarn became fabric and how much fabric became garments, each link’s yield, each company’s margin and the group’s — and the alert when one company sells to another below cost.
In a staging account with simulation on, the invoice goes out simulated without asking for the A1 certificate or the provider token — what demos and training needed to issue end to end. Nothing changes in production.
Spinning joined the textile vertical. Every bale with the SAI code and HVI report (micronaire, length, uniformity, strength, colour, trash, short fibre), crop, gin and ABR/Better Cotton certification; cotton stock now speaks in micronaire categories.
The yarn laydown is built by micronaire category, with weighted average, variation of each property, a traffic light against the specification and the distance to the previous laydown of the same yarn — same as the previous means zero barré in the customer’s fabric. “Suggest bales” fixes it at the lowest cost.
When the laydown is closed, Tenka forecasts yarn CVm, IPI and RKM with a regression over the mill’s own reports and shows the historical accuracy alongside — swapping two bales is decided before the first machine starts.
Report per yarn lot (count, twist, CVm, IPI, hairiness, RKM, clearer cuts, Classimat), typed or imported from the Uster Tester, Classimat or AFIS CSV. Control chart with Western Electric rules, Cpk against the customer specification and each result’s percentile on the world scale.
The contracted range per yarn — and per customer when they ask for something different — serves the laydown (HVI), the lab (Cpk) and the lot certificate. With the percentile scale registered, the customer can specify “CVm at the 25% percentile”.
Contamination recorded in the bale, blowroom, yarn and fabric, linked automatically to supplier, gin and crop — with a ranking of who contaminates and the cost per chain point for the next purchase negotiation.
Every cotton purchase with the quality clause (micronaire, length, strength), price basis (CEPEA/ESALQ, ICE or fixed), premium, pricing and delivery window. Lots point to the contract: delivered volume and HVI come from the bales.
How many months of cotton there are (by micronaire category), how much of the next quarter is still unpriced, the average position cost and the cotton indicator with its 30-day change — with real laydown consumption, not a spreadsheet.
A 0–100 score per supplier: delivered report against the clause, contamination per tonne, punctuality and premium paid — with weights the company defines. Shows in the cockpit and when choosing whom to buy from.
Readings by area with kg produced give each area’s kWh per kg against target; peak demand is compared with contracted demand (warning before overrun) and month consumption is projected against contract volume and flexibility.
The energy negotiation in Commodities gained contracted demand, flexibility, modality (free or captive) and submarket — what the energy cockpit needs to warn of overrun and settlement outside flexibility.
Routes to the customer with delivered cost per kg, road and coastal shipping side by side for the same destination, and a warning when contracted freight falls below the trip’s ANTT minimum. The route cost per kg goes into the delivered yarn cost for each customer.
Anti-dumping catalogue by HS code, country and producer (e.g. polyester fibre, GECEX 910/2026). In the import process, “Calculate anti-dumping” finds the rate and adds the BRL duty to the landed cost — imported fibre competes with domestic at the true cost per kg.
Each lot of polyester, viscose, modal or imported cotton with count, cut, tenacity, elongation, shrinkage and spin finish (or HVI) and the lot decision — the foreign supplier enters the same score as the domestic one.
Records per machine and shift — on the phone or from the spinning monitor CSV — with efficiency, idle spindles, breaks per 1,000 spindle-hours and clearer cuts, against the company targets.
How much of the paid cotton became yarn in the period (against 85–90% carded and 67–75% combed), waste by stage and its value sold as by-product — every yield point is direct margin.
The customer complaint follows the eight disciplines (team, description, containment, root cause, corrective action, validation, prevention, closure) with a deadline — and opens already showing the laydown, bales, supplier and report of the claimed lot.
Prevention, appraisal, internal failure (waste above reference and late contamination) and external failure (complaints) for the period, in Juran’s model — the figure that shows how much investing before the customer’s fabric complains is worth.
At the knitting mill, each fabric lot with weight, shrinkage, fastness, pilling, elasticity and barré against the article range and the yarn lot used. At the spinner in the same group, the fabric report shows on the yarn lot.
In the yarn lab, the “Trace, customer and COA” tab generates the lot certificate of analysis as a PDF — report, contracted range, light and percentile — in the recipient’s language, and shows which laydown, bales, suppliers and gins the yarn came from.
The % of ABR, Better Cotton and organic in each yarn lot comes from the mass balance of the laydown bales — the responsible-cotton claim now has per-lot proof, and the data for the 2028 digital passport is ready from day one.
Cockpit with the yarn cost breakdown — cotton divided by real yield, energy, labour, overheads, cost of poor quality and freight to the customer — and the price suggested by the target margin.
With the value-chain link set to spinning, the owner’s home shows cotton coverage, quarter exposure, kWh per kg, yield and open complaints; the supervisor’s shows efficiency, breaks, idle spindles and yield. “Needs you” warns of low coverage, energy demand, CVm out of control, laydown out of range and overdue complaints.
The spinning lean menu follows the spinner’s day — cotton, laydown, lab, floor and customer, with purchasing, energy, freight and cost — and a long press on the app icon offers Record machine, Read bale and Record report.
New phone screen to record the machine’s shift (kg, hours, idle spindles, breaks, waste) with recent machines one tap away, and to read the bale tag with the camera and see the HVI report before the laydown.
On the tech sheet, the Cost breakdown tab shows raw material, trims, labour, subcontracting and overheads allocated per minute, each one’s %, the suggested price, the margin per channel and standard vs actual from the last work order — and exports CSV and PDF.
In financial categories, the new “Factory overhead” separates factory rent, production energy and maintenance from administrative expenses: the average of these categories becomes the overhead of the cost per minute.
On a confirmed sales order, “Create work orders for what is missing” opens the work order with the missing grid by size and colour, the promised date and the source order — without duplicating. With the parameter on, the confirmation itself creates it.
On the production board, “Sequence by promise” puts each work order in P1 to P5 by the promised date, and the “What goes first” panel shows when each one finishes at the cell’s capacity and what does not fit the deadline.
New Incentive plan screen: fixed pay + capped bonus for cell target, attendance and quality. The Simulation tab shows how much each person would earn over recent months and what piece rate would pay — and applies to the previous month when you decide.
On the phone, the seamstress scoreboard shows the bonus already secured this month under the current incentive plan.
In Production people, the new panel shows absenteeism per cell against the target, turnover, the cost of absences in lost minutes and how much it costs to replace a seamstress. Tenkai warns when a cell goes over the target.
In cell balancing, anyone with an absence, sick note or holiday recorded for today is taken out of the people count, and the screen says how many are out.
New Multi-skilling screen: the cell’s person × operation matrix with the level and actual minutes measured from records, the operations only one person knows and who is learning.
Cell balancing uses people’s actual minutes (with 20 or more records) and suggests who to put on the bottleneck, with the estimated gain in pieces per day.
In phone inspection, the defect photo comes with a suggested type and severity — the inspector confirms or corrects, and Tenka learns from each correction.
On the supplier record, the Approval tab gathers registration, licence, contract, certificates, e-Social and audit with expiry dates — and the subcontractor can send documents through its portal. Tenkai warns when something expires.
When opening a shipment to a subcontractor with an expired or missing document, Tenka asks for the manager’s confirmation — or blocks it if the parameter is on.
New Shop-floor hours and NR screen: overtime per person against the legal limit, short breaks, time bank and the NR-17, NR-12, PGR and PCMSO checklist per workstation with expiry dates. The time clock warns when a punch passes the limit.
On the item, the Passport (DPP) tab shows composition, origin per link, estimated carbon footprint, repairability and recyclability, says what is missing for the European digital passport and downloads the JSON-LD; the QR page gains the footprint and open data.
New Emission factors screen: register your supplier’s factor (fibre, processing, electricity) with its source and it replaces the public reference in every passport.
On the tech sheet, download the tech pack with materials, operation sequence and the measurement chart with tolerances, in Portuguese, English or Spanish — and import the chart by CSV with review.
In phone inspection, check the measurement against the work order’s tech-sheet chart: outside tolerance becomes a “measurement” defect and the check is recorded in the inspection.
In collections, the “Size that comes back” card shows returns and exchanges by size and colour against the garment’s average, with the reason — and goes straight to the tech-sheet measurement chart.
On the collection plan, simulate a rise in fabric, trims, labour or subcontracting and see which garments drop below the minimum margin — with the price that restores it.
On the collection plan, see how many sewers the collection needs each month until launch, against headcount — and what it costs to hire, work overtime or subcontract.
In garment production, each cell gets preventive maintenance (interval and last done), machine stops with their cost and the next maintenance; three machine stops in seven days open a ticket automatically.
In the Household future, simulate the financing (SAC or Price, yearly interest, term) and see the instalment, the income committed, the "can spend today" and the household score afterwards — in three scenarios, with the verdict: fits, tight or does not fit.
On the debt record, enter the rate another bank offered and see the new instalment and how much interest you save to the end — with the step by step of digital portability. Tenka warns you when a debt goes above twice the CDI.
For freelancers, contractors and commission earners: when income varies more than 30%, the budget uses the 6-month median, "can spend today" first keeps 1 month of fixed cost, and in a good month Tenka reminds you to save the difference.
On the phone, 10 one-minute questions each quarter (CFPB Financial Well-Being Scale). How you feel appears next to what the household numbers say — and the gap becomes the conversation question.
Enter the brokerage note trades and Tenka runs the tax calculation: R$ 20k exemption, day trade, REITs, loss offset and the DARF with its due date — plus the 31/12 position for the tax return. On the 20th it reminds you of the DARF.
On the goal, set how much to save and on which day: with Open Finance consent the automatic Pix is scheduled; without it, Tenka reminds you on the day with the Pix copy-and-paste code and QR ready. And "save more tomorrow" makes savings rise with income.
Every month, 5 questions drawn from the household numbers for both of you to answer on the phone. "Only I see" now asks for a reason the account holder sees, and spending above the agreed amount notifies the household.
The allowance splits into spend, save and give; the saved part earns interest every month; and the parent gets a question of the week drawn from what the child did with the money.
On the discovered subscriptions, the scissors show where to cancel, how much the household saves a year and what the law guarantees — or open a ready message to renegotiate on WhatsApp. The request is recorded with the protocol number.
The company offers Tenka Family: with the employee’s authorisation on the mobile payslip, net pay, advance and meal voucher become household income on their own. HR sees only the aggregate — and nothing with fewer than 5 households.
The agent the company builds now acts according to the routine’s policy: just notify, propose for a human to confirm, or execute through the same path as the manual action, within a daily action cap. The trail shows what it did, what it asked for and what it refused.
Ne count, micronaire, Uster percentiles, pieces per sewer, the promised date on the Production board and the month of the collection plan and of energy now follow your language format — decimal separator, thousands separator and month name. Some used to show a dot as decimal or YYYY-MM-DD.
When production records add up to more yarn than the lint in closed laydowns (yield above 100%), Yarn cost uses the benchmark yield and tells you what to check, instead of suggesting an unrealistic price per kg.
The Financial health screen — with the household’s perceived well-being next to the score — and the well-being questionnaire on the phone are now part of the Finance module and included in the Family plan.
In the Monthly talk, Can I buy it? and the debt payoff plan, the surplus is what comes in minus what goes out in the month. The money kept in accounts used to be added, the surplus looked huge and the simulator even suggested paying cash.
New screen Spinning → FX desk: how much the mill owes in dollars and when (dollar lint to be delivered, imports in progress, foreign-currency bills), how much is protected by hedge, receivable or foreign-currency balance, coverage per window against the company policy and the hedges’ mark-to-market at PTAX. Hedges (NDF, dollar futures, option, bank lock, ACC/ACE) are recorded linked to the contract or import they protect.
On the FX desk, each lint contract to be fixed shows the yarn cost per kg if fixed now against the average already fixed, and how much each cent of ICE and each R$ 0.10 of dollar move the yarn. Triggers alert when cotton or the dollar reach the target, and the Central Bank PTAX comes in by itself every 6 hours.
New screen Spinning → Yarn margin: each yarn sale in the period with revenue, cost and margin, grouped by count, customer or lot. The kg cost comes from the lint mix of the lot sold plus shop-floor costs.
Yarn sales contracts with the base price adjusted by lint, dollar and energy by the agreed weights; the list shows today’s price of each contract.
The yarn cost gained the lint ±10% × dollar ±10% matrix with the margin in each combination, the dollar that wipes out the margin and the non-creditable tax left in each kg today and under IBS/CBS, by the percentages your accountant provides.
New screen Spinning → Maintenance: plan by machine and component with an interval in running hours (summed from the log since the last replacement) or days, what is due soon and overdue, the "done today" button and the machines breaking above the stage average.
New screen Spinning → Investment case: does the new machine pay off? Productivity, energy, people and waste against the investment, after-tax NPV, IRR and payback under straight-line and accelerated depreciation (Law 14,871/2024 — eligibility by the accountant), and the financing instalment.
New screen Comex → Drawback: the grant with type, validity, export commitment and import limit. Linked processes give exports, imports and suspended taxes; a grant with an export balance and less than 90 days to expiry shows as at risk.
The comex process gained the LI date, the FX closing date and the drawback grant, and shows the whole timeline. In the anti-dumping catalogue a row can be suspended (public interest), with reason and review date — it stays visible and does not enter the import cost.
New screen Spinning → Imported yarn parity: each origin’s yarn landed here — FOB, freight, insurance, II, anti-dumping and costs at PTAX — against our price, with protection in % and lead time.
New screen Spinning → Crop contracts: forward buying at origin with planted area, expected yield in lint arrobas per hectare, tonnes, price basis and certification. The list shows whether the field covers the contract and how much has arrived.
New screen Spinning → Lint receipts: every truck with the gin’s packing list against the mill’s count and scale, and weight shrinkage totalled per gin. The HVI import also accepts SAI/ABRAPA standard columns.
New module Knitting and Weaving: machines, production by machine and shift (kg, rolls, hours, stops, rpm) and 4-point inspection recording the machine and the yarn lot. The panel shows efficiency by machine and quality by machine and by lot — barré goes back to spinning with the right lot.
Each fabric article says how much of each yarn it takes (share in %) and the process waste: the yarn needed for an order comes out of the calculation, and spinning knows what knitting will order.
New module Finishing and Dyeing: dyeing recipes, batches by machine with water, steam, energy, ΔE and re-dyes, and the panel with right first time (RFT), re-dyes and cost per kg by machine and colour.
The dyehouse settings (cost of a m³ of water, a tonne of steam and a kWh) enter each batch’s cost per kg together with the recipe chemicals — every re-dye shows in the cost.
New screen Spinning → Machine monitor: connect the manufacturer’s monitor (Rieter, Trützschler, Uster, Loepfe, Murata) with the encrypted token and the field map. In the log, "Pull from monitor" brings the last 7 days into the same review as the CSV — nothing is saved without your OK.
In the collection plan, when the planned mix goes above 1.5 times the sales target, the plan card warns with the mix value, the ratio and the target — a sign that the target is too low or the mix is too large.
In Settings ▸ Artificial Intelligence, in Tenkai Usage and in the Library, the texts that still showed in Portuguese (months, period, totals, key modes, subjects) now appear in the reader’s language. And the reason prompt of "View data" now says which company you are entering.
Labels, card titles, headers and helper texts written directly on the screen still showed in Portuguese for anyone who chose another language — about 1,800 snippets on more than 300 screens, including the customer portal, mobile and the password screens. They now appear in the reader’s language. So do the menu axis subtitles and the top search.
With the two-way connector on, the order confirmed on screen, on the B2B portal or in the sales rep app goes to the ERP and comes back in seconds with the ERP number. Before sending, Tenka checks stock and credit in the ERP itself; if the ERP rejects it, the reason shows on the order and it can be resent. Everything sent, waiting or rejected is in Integrations ▸ Orders sent to the ERP.
On the portal the store sees the same order status the rep sees in the ERP (pending, released, invoiced, delivered), step by step; the credit limit with how much it can still buy; and the duplicate of the slip issued by the ERP — payment line to copy, Pix and PDF with the barcode. The footer says how long ago the ERP data was updated.
The customer sees on the portal the points or cashback balance that counts on the next order, what expires in the next 30 days, the program rules and the statement. A company that already had a program in the ERP brings each customer’s balance in a checked load, with nobody losing points.
The portal customer gets a phone notice when the order status changes (including in the ERP), when a slip is issued and 3 days before and on the due date, when they earn or use rewards and when the limit changes — in their language and only what they left on. The company sends push campaigns to everyone or to one rep’s portfolio, with a weekly cap of campaigns per person.
Without signal, the portal shows the last copy of orders, bills, limit and rewards balance, and the sales rep app shows the portfolio with open amounts and last purchase — always with the time of the copy and a note that it may be out of date. The copy is encrypted on the device, expires in 24 hours and disappears when the person logs out.
The rep checks what is available for any article by warehouse, before and during the visit, without choosing a customer. The order placed in the app — including one saved offline — goes to the ERP after rechecking stock and credit.
The customer asks for a sample, pattern or pilot piece on the portal, with article, colour, quantity and deadline, and follows it like a ticket. In the B2B order, each article shows the technical sheet: composition, weight, width, yield per kilo and shrinkage.
Each account invited by the partner’s program can have its plan paid by the program (default) or by the store. The partner gets one consolidated charge per month; switching takes effect next cycle and whoever stops being paid for is told 30 days ahead.
The Tenka app is ready for Google Play and the App Store through the platform account: a single app that dresses in each company’s brand at login, with phone notices on the iPhone too. Publishing depends on the platform’s developer account.
New screen Sales ▸ Textile chain map: from order to cash, each stage (sales, planning, spinning, knitting, dyeing, garment making, stock and shipping, tax, finance, after-sales and ERP) is a box with your company’s numbers, and the arrows show what feeds what. One click opens the screen.
The anchor partner also sends the portfolio invite via WhatsApp, with the message ready, and resends at once the invites unanswered for 7 days. In the bulk invite you can state each account’s sales rep, and the portfolio filters by sales rep.
With the order written to the ERP and the charge in the ERP, Tenka invoicing does not create another receivable: the bill is created in the ERP and shows here through the finance read. The choice lives in the parameter Portal: payment method for online purchases.
Credit limit, open amount, bills, benefits balance and statement amounts show for the customer on the portal — before they appeared masked as "•••", because the see-amounts rule for company staff also applied to the customer.
Saving the parameters screen stores only what you changed; the history no longer fills with dozens of default-value rows and your change shows at the top. PORTAL.PAGAMENTO and ERP.ESTOQUE_SEM_SALDO became option lists.
Typing "30/09/2026 10:00" in a date-time field stored the year 0020 in some forms (scheduled campaign, time entry, ticket estimate, records). Dates now keep the full year on every screen.
The "You are in" trail, the title and the Recents of new screens (orders sent to the ERP, textile chain map, push campaigns, spinning screens) appeared in Portuguese for people using another language. They now appear in the chosen language, as do form sections.
At the knitting mill, the map now shows the numbers of the same group’s spinning mill (bales, lab reports, blends) without switching companies; the Sales reps box counts the registered reps.
In the sales rep app, choosing the customer and checking stock gave an error; they now work, and stock shows only what is truly available per warehouse (no negative balance).
If a network supplier invited you and you accepted, every invoice they issue reaches your incoming invoices, with the supplier already registered. You check and post — only then does it enter stock.
The portal has a "?" button at the top: each screen opens its article in the Help Center, in the customer’s language, and the Help Center now has a Customer portal section.
Every app screen has the "?" button with the same help as the computer, and screens with a tour invite you to explore them on the first visit. App colours now come from the same system tokens.
The fields’ ⓘ tip, the "Yes/No" in lists and filters, the plan name and the guided tour buttons appeared in Portuguese in any language; they now follow the reader’s language.
In the sales order catalogue window, the price shown is now the customer’s table price — the same the line gets — and the total in the Items tab updates as soon as you add.
The actions menu on each row of the Tickets and Service calls lists now shows "Start timer". With the timer running on that ticket, the same item becomes "Stop timer" and logs the time. It is the same timer as My Schedule: what you start in one place shows up in the other.
The tax reform calculation now adds up the IBS and CBS shown on the month's authorized NF-e and deducts what was shown on the purchase invoices you recorded. Items with zero rate or reductions pay what the law says, and credit larger than the debit becomes a credit balance for the next month. While the company does not issue invoices with these taxes shown, the estimate from revenue remains — now with the purchase credit.
Each component of the bill of materials gets its normal loss in % (spreading leftover, yarn ends), and the standard cost, MRP, piece price and the work order issue already include it. And you set alternative items: if the yarn in the bill runs out in the warehouse, the issue uses the alternative, in priority order, and records which component it replaced.
In the item record, the "SPED item type" field says whether it is raw material, finished product, packaging, goods for resale and the other types of record 0200. Items in a bill of materials are already classified — the product as finished, the component as raw material; the others stay blank for you to classify with your accountant.
The Production process screen keeps the sequence of steps — cutting, sewing at the subcontractor, bar tack, finishing — with resource, standard and setup time. In the bill of materials, "Apply process" copies the steps to the routing, and every new work order is born with them.
Each step can have the work instruction, a checklist and the "requires scrap reason" rule. On the work order, whoever reports sees the instruction, confirms the checklist before reporting good pieces and gives the scrap reason — loss by reason shows where the loss is born.
An external step carries the third party that does it. On the work order, link the step to the processing shipment that took the lot: when the subcontractor's return is recorded, the step moves by itself — what came back counts as good pieces and the loss as scrap.
In Digital books, the "Block K" button generates the month's file: items and the bill of materials with loss, inventory by possession (yours, yours at the subcontractor and the customer's with you), each work order's production and consumption, what came back from processing and, if checked, the inventory. The check comes along: an item without the SPED type is left out (never guessed), and the system warns about items without NCM, negative balances, work orders without consumption and consumption outside the bill.
The Lead times tab shows, for the last 90 days, how long each method takes from dispatch to delivery — courier, carrier, app and own delivery — how many arrived by the next day and how many failed. And Tenkai answers "which method delivers fastest".
On the driver's phone, without network, each stop's delivery now also keeps the photo and the recipient's signature. Everything goes up together when the connection returns, and the proof stays on the shipment as if it had been done online.
In the sales channel, turn on "Send Tenka's stock to the store": every 30 minutes, the available quantity of each size and color goes up to the store — only what changed. It comes off; turn it on when Tenka is the source of truth for stock.
In the production process, drag the steps to change the order and see the flow drawn. Neighboring steps with the same parallel group run together (embroidery and printing at the same time), and a step can send rework back: scrap in it reopens the chosen step on the work order.
The work order shows the cost of each step: the material that goes into it, the hours at the department hourly cost and the subcontractor service. A step can deliver a semi-finished good (cut piece, sewn piece) that enters stock at the cost accumulated so far. And scrap above the tolerance no longer makes the good pieces more expensive: it goes to expense, shown separately.
In the IBS and CBS calculation, a purchase credit counts as you pay the supplier, as the law requires; what is still unpaid is shown separately and does not offset. When the credit exceeds the month tax, the surplus becomes a balance and offsets the next month. And IBS credit offsets only IBS, CBS credit only CBS.
On the work order, each input shows the BOM standard (already with normal loss) and what actually left stock, with the variance in red when it went over. And you can ask Tenkai "where is the bottleneck?" — it tells you which step the lots are stuck at and which step takes longest or scraps most.
In the customer record, say how much they can owe. An order that goes over the limit — adding what is open and the orders not yet invoiced — is not confirmed, and the message shows the numbers.
In forms, the date can now be typed (01/10/2024) or picked from the calendar. If part of the year is missing, the field warns you right away — nothing is saved without a date.
An item in the trash is not offered for new choices; the "We recovered what you typed" notice no longer returns after saving; buttons at the end of the page are no longer under the footer bars; and a new account already starts with payment types (boleto, Pix, cash).
Whoever creates a family account sees only what they use at home — budget, accounts, cards, goals, income tax — and not the business screens. "Show all" is still one click away.
Type the ZIP code of a customer, supplier or any record with an address and leave the field: street, district, city, state and IBGE code fill in by themselves. What you already typed is never replaced.
The supplier record now has a full address, state registration (or EXEMPT) and the category of what they supply — raw material, trims, sewing contractor, service, transport, resale, packaging. That is how you find "who sells me fabric".
In the item’s textile attributes, write the composition as on the label: "100% cotton", "96% cotton, 4% elastane" or "cotton 60% / polyester 40%". Tenka organizes it and still checks that it adds up to 100%.
When something is missing, the message says which field ("Name: must not be blank"). And no message shows technical database text anymore: the detail goes to the support log and you read a sentence you can understand.
When you send to the trash a record others use — the account that pays the card, the person with entries, the category with a budget — the notice says how many entries, cards and goals were linked to it. A mistake? Undo is right there. And removing someone from an access group now asks for confirmation.
The "Home" center the account creates (and any group that contains other families) counts as a shared area in the settlement, never as an extra family. The forecast warns when the balance already starts negative. "Close statements" also closes old statements for spending entered with past dates. Months are spelled out. And marking an entry as Paid asks for the account and records the payment date and amount.
The apparel maker opens Tenka and reads collection, tech pack and sewing contractor — not contract and hours; the first steps tick when the item, the production order and the order are actually created; the customer record hides license and subscription tabs for those who sell garments. The family sees "Household documents" with personal documents, "People and groups in the household" and access examples like "Kids".
The 30-second survey no longer shows up for newcomers or on top of a form being filled in; and closing it with the X counts as "later" — it doesn’t come back at every login.
If something failed in the middle of sign-up, the e-mail got stuck: login said there was no linked company, a new attempt said the e-mail already existed, and there was no way out on screen. Now the account is linked to you from the start and, if a final step fails, just sign in with your e-mail. On the form, the company name no longer disappears when you leave the document field, and the password stays filled in when the screen points out an error.
An invoice typed by hand and then imported from XML (or imported twice) is refused: the same supplier, number and series already have an entry. And "Check" compares each item with what the order still expects — 1,250 m on an invoice against 1,200 m ordered becomes a discrepancy, not "ready to post". An order that has already received goods can no longer be cancelled, and cancelling asks for confirmation.
Completing a production order step now requires knowing how much came out of it — good or lost pieces. An empty closed step zeroed that phase’s cost and passed on a batch nobody counted. For the sewing contractor’s step, the quantity comes from the shipment return.
The stock movements list (and the other screens whose document stores the company directly) now shows, opens and deletes only what belongs to the company you are in.
In bulk payment you can type the date or mark each item paid on its own due date — the right way to enter history; if the date is more than 60 days from the due date, Tenka warns you. A goal past its deadline says so and how much is left, instead of asking for an impossible installment. The family’s bell alerts no longer talk about margin and break-even, compare the month that has closed and show percentages properly. The 13th salary has its own category and column in the family income tax report.
In a family account, the phone home and the thumb bar show what the household uses on the go: log an expense, envelopes, statements, what’s coming, goals and ask Tenkai — no time clock, hours or payslip.
When the shipment to the sewing contractor is linked to a production order step, what was shipped already counts as the order’s consumption (component issue doesn’t take it again), the batch cost includes the shipped material, and the returning garment enters stock through the order completion — by variant and at the computed cost, not through the return at zero cost. The linking list shows all open shipments (the process contractor’s first) and hides those already in another order. In the contractor portal, shipped quantities show by unit and the finished quantity can’t exceed the order’s pieces.
Choosing the tech pack fills the item to produce, and the order won’t accept an item different from the tech pack’s. Completing the order with a step still open is refused (the message says which), and the batch cost shows in your currency format.
A business account now starts with the basic financial categories of its industry (for apparel: raw material, trims, sewing contractor service, payroll, rent, taxes, freight…), so the first bill already has a place to go. And an item with the same name as one already registered is refused — sizes and colors go in the item’s grid, not in repeated items.
A card purchase goes into the budget, envelopes and the month’s result in the month it was made (each installment, in its month) — not in the statement month. The statement stays the same. When you log an expense in an envelope that passed 80% or went over, the phone tells you right away.
The sales order has a Size / color column for items with a grid — once the item is chosen, the screen offers its variants. Adding or removing a line no longer erases what was typed in the others, and the list shows the customer name, not the code.
Sales returns now have order, customer and warehouse fields, types and statuses show up, and Process works (or says what is missing). An exchange is no longer half-saved: if the pieces can’t go back to stock, neither the exchange nor the voucher is saved, and the screen says why.
Stock refuses movements in a warehouse that isn’t from your account — and the POS warehouse accepts the code shown in the list. With no warehouse set, the POS warns before closing the sale (instead of selling without reducing stock), and "Sell without invoice" is unchecked after every sale. The incoming invoice always creates the bill to pay, creating the basic category and type if the account lacks them.
A production order with a sewing contractor now adds to the cost the material shipped to the contractor, and puts into stock the good pieces from the last step. A shipped order shows as dispatched in the Shipping hub, instead of "waiting to leave".
In a Family account, Home no longer shows tickets, projects, business maturity or modules to "unlock". The strip became "The household today", with what came in this month, the payer card uses that voice, and the first step "Add your team" goes to Access — so each person living in the house records their own spending.
Home, "+ New", the axis shortcuts and suggestions now offer only screens your profile can see AND your plan includes — some used to land on "part of a higher plan". The "You haven’t opened yet" suggestion no longer points to technical screens such as the Error Log.
Manual movements, transfers, stocktaking ("Count by grid"), returns, exchanges and the POS now state which size and colour moved. The POS finds the piece by the tag’s SKU or EAN and warns when that variant is out of stock. Stock per variant now counts adjustments and transfers.
An order for a product with a grid gained the "Order grid": how many pieces of each size and colour the batch makes. Sewing bundles follow that grid and completion posts stock by variant — before, an order for a product with a grid could not be closed.
A shipment to a sewing or dyeing contractor now generates the shipment NF-e (5901/6901). The return records the contractor’s return invoice, accepts a different item in another unit (kg of fabric coming back as pieces), states the variant and enters stock at the cost of the material consumed plus the service. A shipment with leftovers at the contractor can be closed, with the reason.
The shipping hub, delivery manifests and the fleet moved to the Sales module, next to shipping. Anyone already using them still sees them; the menu is now in one place.
Each person’s form in the household gained relationship, birth date and "income-tax dependant". The family income tax shows each person’s dependants and deducts the legal amount per dependant in the monthly tax.
Each suggested settlement can be marked as paid, with the date, and undone if it was a mistake. The month no longer shows as pending what was already settled.
The Family account Home shows what is due in the next 30 days — bills, card invoices and documents — with overdue ones in red. Tenkai answers "what is due this week?".
The family’s homes and cars have what they are worth today, what is still owed and who owns them. Net worth uses market value and subtracts the financing; the form no longer asks for depreciation.
The maturity panel on Home now measures what your line of business does: the household by accounts, people, entries, budget and rules; apparel by spec sheets, sizes, orders, contractors, sales orders and shipping.
Questions like "how much did we spend on Pedro in 2025?" answer with that person’s spending in that year, even when AI is off — before they came back "not found".
In item tabs (stocktake, invoices, spec sheets), quantities showed as "4.000" — read as four thousand in Portuguese — when they were 4. They now follow your language, without trailing zeros. The POS cart too.
A stocktake opened from the list did not show "Apply stocktake" or "Count by grid". Both appear whenever the stocktake is saved and open, and the line counted by grid shows the size and colour.
In the production order, "Complete step" could reply "Step completed." without changing anything (the step had already been completed by another click). Now the message only appears when the step is actually completed; otherwise the screen warns you and refreshes the list.
The Partner portal could open cut off, without the end of the page. It now opens complete — and the same fix applies to any screen that depended on the module name in the top path.
In a new entry, "Movement type" already said "Income" before you chose the category. It now stays blank and shows Income or Expense as soon as the category is chosen.
New Visual management screen: each cell with today’s pieces against the target so far, efficiency, OEE, minutes stopped and who is stopped and why. Refreshes every minute and has a "TV mode" for the factory TV.
In "My pieces" the sewer taps "I stopped", chooses the reason (missing material, machine, waiting for cutting, model changeover, quality, absence) and "Back" on resuming. The stop shows up at once on visual management and counts in OEE.
"My pieces" now shows today’s pieces, how much of the daily target that is, what the production is worth and the pieces of the last five days. The target comes from the person’s record or the cell’s target divided by its people.
New Balancing screen: choose the style and the cell and see how many people each operation needs, which is the bottleneck and how many pieces a day you can promise. "Use as target" saves pieces per hour on the cell.
The sewing bundle ticket code is now read by the phone camera, in "My pieces" and on the shop floor: the bundle quantity is recorded by itself on the step in progress.
The inspector checks on the phone: where the pieces come from (order or subcontractor return), seconds, defects as chips and the photo of the defect. Approved pieces are calculated, and the subcontractor discount goes to the service bill.
The live size grid gains "Can I deliver by": pick the date and each size and colour adds to today’s available what production delivers by then. On the sales order, the trail says whether the promised date works. Late orders or subcontract work do not count in the promise.
Size grid and store gains the Conflicts tab: variants with more orders than stock and who gets them by the house rule (nearest delivery, key customer, highest value or first come). "Move ahead" swaps the reservation with a reason written on both orders; the customer gains "Service priority".
The collection link (the same as the lookbook) lets the retailer pick pieces by size grid and place the order with tax ID and mobile, no login. It arrives as a quote with the customer’s B2B price list and you get a notice. Turn it on in Parameters ▸ Sales.
A style with a size grid opens size × colour with "spread by curve"; the portfolio shows who bought this month, who is cooling off and who is near you; picking the customer shows open, overdue, credit limit and last purchase; and without internet the order is written down and uploads by itself when the network returns.
Photograph the paper order on the sales rep’s phone: Tenka reads it and shows what it understood before adding. On WhatsApp, "pedido para Trama Urbana: 20 BV-2210 M preto e 10 G branco" becomes a proposal with size and colour, saved with CONFIRMAR.
The sales rep panel and the phone show how much to sell TODAY to hit the month (what is left ÷ working days) and how much came in today. The Sales reps screen gains the month’s ranking of reps and of the counter (POS).
External processing shows, per subcontractor, on-time returns, average delay and late open shipments next to the quality score. On the shipment, one tap chases the subcontractor on WhatsApp with the message ready.
On the Collections screen, switch Grid to Board and drag the piece from Idea to Sample to Approved, with the photo on the card. Approving creates the item with its grid; rejecting asks for the reason.
Without anyone asking: late subcontractor, production order without material, order that will be late and size about to run out arrive in the bell and in the "Needs you" card on Home. Ask Tenkai "what needs me today?".
In apparel, the owner sees the company’s day, the supervisor sees production right now, the sales rep sees target and portfolio, and the seamstress goes straight to "My pieces". In "See the Home as" you choose another.
Press and hold the installed Tenka icon: in apparel, Log pieces, I stopped and Scan bundle; at home, I spent and How much I have.
Each item can have purchase and sale units besides the primary one — box of 12 or 24 per size, gallon, gram for an item in kilos — with their own factor, price and barcode. Purchase orders, supplier invoice entry, sales orders, the POS and invoices use the chosen unit, and stock always converts to the primary unit. With no factor, the operation is refused instead of assuming 1.
On invoice entry, the invoice unit is matched to the item record; when it does not match, the screen asks for the equivalent before posting. A box of 12 is received as 12 units, at the cost per unit.
In the item record, the new "Kit composition" tab marks the item as a kit and lists its components (with size and colour when they have a grid), the cost of each, the kit cost and how many kits today's stock can assemble. Selling the kit at the POS or through a sales order deducts each component; returns and exchanges put them back. A kit without components cannot be sold — the sale is refused with a notice.
The kit cost is recalculated whenever a component's cost changes, and it is what appears in the order margin, in the price-list update by cost and in the item valuation.
At the POS, Sell gift card: any amount, code on the spot and 12-month validity (parameter VALE.PRESENTE_VALIDADE_MESES). The amount is posted as an obligation in Gift cards to redeem, with no goods invoice; revenue is recognized on redemption or when the card expires. In Sales ▸ Gift cards and rewards: balance, lookup by code, cancellation with reversal and expiry.
Turn the program on in the BENEFICIO.* parameters (cashback in % or points per currency unit, validity and minimum to redeem). A paid sale with a customer credits the balance; exchanges and returns reverse it; the customer uses the balance at the POS paying with Rewards. The balance shows on the customer record, in the portal (My orders) and in Tenkai.
In the contract, the category, the bill type and the profit center appeared in two places, and saving could undo your edit without warning; the same happened with the areas served in the studio acceptance. Now each field is edited in one place only, and what you changed is what gets saved.
With two tabs open or a double click, saved permissions and filters could show up half-loaded for a moment. Now every screen always sees the whole session.
Creating a new account makes far fewer trips to the database, and the returns list no longer loads every order and customer just to show each one's name — in large accounts it opens in a fraction of the time.
The new Block K screen (Accounting) shows, before generating, how many lines each record gets, what was left out of the file and why — item without SPED type, without unit, without NCM, unit without factor, negative balance — and a preview of the lines. It also compares the previous month’s generated file with the inventory recalculated today and takes the difference to the correction with one click.
The Block K file now includes 0220 (conversion factors of the item’s alternative units), K220 (when one item becomes another without a work order — posting moves the stock) and K280 (correction of the inventory of a month already filed, with the reason). Both entries are made on the Block K screen.
On the Block K screen you choose the file: only Block K and the inventory for the accountant’s system, or the whole EFD ICMS/IPI — opening with the company and accountant data, input and output invoices (Block C), ICMS assessment with the amount to pay (Block E), inventory, Block K and the Block 9 counts checked. The check shows each block, the assessment and what to fix before generating.
The Block K file now comes out with state, city, profile and activity in the opening record, with the K010 record (layout type, mandatory since 2023), with the inventory before Block K (the official order) and with the Block 9 count including the closing record — points the Federal Revenue validator used to reject. The count fix also applies to ECD, ECF and EFD-Contribuições.
When you opened a bill of materials or a shipping manifest, the top of the screen had no title and no "You are in" path. The form now shows the screen name and the way back to the list, in your language, like the other documents.
In the add-item window, the search shows results and the cart receives what you pick; on the Payment tab, the summary (total, sum of methods and what is left) follows each value you type, and changing an existing method enables Save.
In the financial entry (interest, fee, discount) and in the strategy and cash flow screens, leaving a value field recalculated endlessly and the screen stopped responding. It now recalculates once, only when the value changes.
Clicking a date field opened the calendar and stole the focus — what you typed disappeared. The focus now stays in the field: type the date or pick it in the calendar; the down arrow enters the calendar from the keyboard.
With Tenka in French, English or another language, screen titles (forms included), the "You are in" path, the area name and the three answers of the day on Home still came out in Portuguese. They now follow the chosen language, like the menu.
Gift card validity and other labels no longer stick to the value; gift card and customer credit messages show the amount with the currency symbol; a POS sale paid in cash, Pix or card creates the entry with that method’s type (no longer "Bank slip"); the piece price scope shows as Product, Product group or Collection; and the e-invoice environment shows as Production or Testing.
Sales and purchase orders recorded before alternative units had the line marked "UN" even for items sold by the piece, and saving again showed "no factor for unit UN". Those lines now state the item's own unit — no quantity changes — and a new line without a unit starts in the item's unit.
In an order not yet saved, adding items through the "Add item" window (or adding and removing lines) cleared the customer, warehouse and payment term already chosen and disabled Save. Now only the item grid and the summary refresh; what you filled in the header stays, and Save is enabled. The same applies to returns.
An order created without a warehouse (like those from the production suggestion) got stuck: completing it asked for the warehouse and there was nowhere to enter it. The field now appears in the order detail while it is missing.
The status of purchase orders and outgoing e-invoices, the e-invoice environment, the request status on Home, the piece price title and the side panel of lists (Yes/No and numbers in your format) now show with labels. A cash sale at the POS creates the entry as "Counter sale", and the required-field messages of an entry speak the Family edition’s language.
In the household budget, recurring charges (streaming, gym, phone) show up with the monthly total and alert you when they go up. One tap makes it a fixed bill; another says “not a subscription”.
Mark an envelope to roll over: what is left of Leisure in September stays for October. Car tax, property tax and insurance go into Annual household bills and become “save this much a month”.
The household budget and “I spent” show how much you can spend per day until month-end, already net of the year’s bills and goals, and what this household costs per month — with the share of income already committed.
Unprompted: “at this pace, Groceries runs out on the 22nd”, “unusual charge at the pharmacy”, “the same purchase entered twice” and “3 uncategorised expenses”. Nothing changes on its own — the alert arrives in the bell.
The month’s spending now shows how much went to essentials, necessities and extras, and the budget warns when fixed costs exceed 70% of income. The household’s default categories come already marked.
Financing, loans and revolving credit in one list, with the interest still ahead, “prepaying $X saves you $Y” and the order to pay (snowball or avalanche) with the month’s surplus.
In a Family account, Financial health and the household budget show the household score: reserve in months, committed income, expensive debt, saving and forecast — and the three things that raise it most.
New Household future screen: saving so much a month, when you reach the goal; how long the wealth lasts with a withdrawal; and this household’s freedom number — in three scenarios, always as an estimate.
In the household budget, “Share” creates an image with income, spending, surplus, the biggest categories and the envelopes; on the phone it goes straight to WhatsApp. Without value visibility, percentages only.
On the household member’s card, “Invite to the account”: the person gets the invite, sets the password and logs in seeing the household and logging their own spending — without touching settings.
Tick “Only I see it” on an account or card: only you and the household owner see it — the rest of the family does not. The owner’s net worth still adds up.
The child has the piggy bank on the phone, the goal of what they want to buy, chores that pay and an “ask for money” button — which you approve or decline in one tap.
On the investment card, the Assets and dividends tab: stocks, REITs, ETFs and crypto with the daily quote (with a provider set up), dividends typed in or from the B3 CSV, and the return vs CDI and IPCA.
Import the bill CSV on the card, or forward the bill e-mail to the household inbox: purchases come in categorised and the same bill twice does not duplicate.
Point the camera at the receipt QR: the store (and the amount, on the offline QR) come in, and the same receipt is never entered twice.
Send the phrase on the household WhatsApp and Tenka replies with the category, for whom and how you paid — saved with CONFIRMAR. In the app, the “I spent” microphone does the same.
Tenkai and the help now find the right article even when it does not repeat your word, adding search by meaning to search by keyword. It starts working once the installation has an AI key with an embedding model; until then everything keeps searching by keyword, with no error, and the Parameters screen tells you where things stand.
With providers that accept at most 128 tools per question, such as OpenAI, Tenkai now sends only the ones related to the question, without exceeding the limit. Before, the question could be rejected and retried, costing twice as much.
Each NF-e item now carries the IBS/CBS tax status (CST) and the tax classification from the item record, with the tax base. In the default mode the tax provider's official calculator computes the amounts; in manual mode the invoice goes out with the state IBS, municipal IBS and CBS rates and amounts calculated here. On for test (homologation) invoices; in production, after validation.
If you sell by the box, bale or gallon, the NF-e now carries both units: the one sold (2 boxes of 12) and the taxable one, the item's primary unit (24 units), each with its price. And the invoice sent is exactly the one that was built, even if the order changes later.
Admins who live in a company's own group (not the Administrators group) stopped seeing screens created after August. Now whoever runs the account sees every screen the plan offers — including those that arrive in a new version or an upgrade. Seeing is not editing: add, change and delete buttons are still granted per group.
The LGPD Center, Privacy, Portability, Retention and LGPD Management had left the plans on sale when they got their own module. They are back in every plan: complying with the LGPD (Brazil's data protection law) is every company's obligation.
A hired digital employee works without another switch: the "digital employees" parameter starts on. To stop them, turn it off in Parameters › Tenkai; actions that affect a customer or supplier still start off, one by one.
Each GB above the plan's quota is now charged at the list price, R$ 1.50 per GB (minimum of R$ 10 in the month), on every paid plan. The amount shows in Storage usage before the invoice. On the Free plan the excess is not charged.
Home used to open with a grey screen and only show the numbers a few seconds later. It now opens in one go, numbers included — and the Overview spreads the cards over balanced rows, with no one or two left alone at the bottom.
On each area hub, the note about where the records live came out with words stuck together and at half width. It is now a single translated sentence that spans the full width of the screen.
The "Most viewed" and "Recent" shortcuts could open an empty form, as if it were a new record (e.g. sales order). They now take you to the screen's list, where you find what you were working on.
At the POS, with the customer chosen, the Customer credit method shows how much they have and uses what expires first; if the sale fails, the credit comes back, and above the balance the sale is refused. An offline sale with voucher, rewards or credit is now checked and deducted when it reaches the server.
Returning or cancelling an order — or exchanging a POS sale — paid with customer credit returns the amount to the same vouchers it came from: an advance payment becomes an advance payment again and its obligation reopens, instead of turning into a new voucher with an expiry date.
The bill of materials now opens like the other records: a list with search, filters and trash, and the sheet with components, routing, measurements and alternatives in tabs, every line editable. The Save button at the top stores the whole sheet at once — before, what you changed in the routing, measurements and alternatives of an open sheet was not saved.
The packing list got the standard list (search, status filter, views, export and trash) and opens as a document, with the lines and the closing in a tab. The number is generated when left blank and each line shows the item name. A closed packing list cannot go to the trash: reopen it with a reason first.
In the shipping center the Melhor Envio label now goes all the way: quote, buy, print and reprint, follow tracking (through Melhor Envio’s automatic notice and every 30 minutes) and cancel — the amount goes back to your wallet and the shipment returns to ready. If the internet drops mid-purchase, Tenka finishes by itself without buying another label; if the balance runs short, it warns you and the Finish label button picks up where it stopped. Sandbox or production is chosen in the integration.
The ride ordered through Lalamove is now followed by Lalamove’s own automatic notice (driver on the way, picked up, delivered, cancelled) and can be cancelled from inside the shipping center while Lalamove allows it. The bell button registers the notice address at Lalamove for you.
With the notifications address registered in your Mercado Livre app, a paid order enters Tenka right away (the search every 30 minutes stays as a safety net), the Mercado Envios label is downloaded and attached as soon as the shipment is ready, and shipped, delivered or not delivered update the shipment. On the channel screen, the Test connection button checks the authorization.
Each shipping integration got the Test connection button, which says clearly what is missing when the credential is incomplete (and shows the Melhor Envio wallet balance). The new Calls and queue tab, in the shipping center, shows every call made and every notice received — without token or secret — and what failed because of the network, with the Reprocess button.
The piece price now has a date: in Prices per piece, set the price (or just the margin) of a product, a product group, a collection or general, with start and end. The most specific one applies — product, then group, collection and general — and a new validity closes the previous one the day before. "Save" on the Garment price screen opens the price from today, and your current prices were already brought in as open validities.
Order, POS, sales rep, portal and consignment now look up the piece price valid on the document date; price list, promotion and discount authority still apply on top. The item record gains the Product group field, which is what links the piece to the group price.
The menu, the hub and the top path (for example, in the Household cash flow) said "Receive", a business word. In the Family edition the area is now called "Household money", with the question "How is the household money doing — will it run short?", in your language.
Invoiced sales orders showed a zero fulfilled amount. Now fulfilled is the invoiced amount, the list shows the invoice number with a link and, when the order was invoiced in parts, "+N" opens every invoice. In the order, the Invoices tab shows total, fulfilled and what is left to invoice.
The order accepts several payment methods — Pix, bank slip in instalments, card, cash, gift voucher, cashback — each with amount, instalments and terms, adding up to the total. On invoicing, each method becomes its own receivables, one per instalment; the 30/60/90 terms now generate the three instalments.
Accounts with no payment terms registered saw the field empty on the order. Now they get the default terms (Cash, 30 days, 30/60, 30/60/90, Down payment + 30/60). Each order item also shows the warehouse it ships from and accepts the lot.
In the sales order, "Add item" opens a search window by name, code, EAN or SKU, with photo, price, the size and colour grid and available stock by company and warehouse. Pick several items with quantities in a cart and add them all to the order at once, already at the customer's price list.
Sales ▸ Payment terms: create "28/42/56", "Down payment + 5×" or whatever term your customer asks for, setting the instalments, when the first is due and the interval. The sales order starts offering it and invoicing creates one receivable per instalment. Terms coming from the ERP show in the list as read-only.
On the sales order, each item chooses which warehouse it ships from (empty = the order's): the reservation marks that warehouse's stock, shipping deducts from it and the line shows how much is available there.
Paying the order with a gift voucher or cashback now deducts the balance, just like at the POS: confirming checks it covers, invoicing debits it (and the receivable for that part is created settled) and a return gives it back. The Payment tab also sells gift vouchers to the order's customer.
On the sales order, Pix, cash and debit card have "Received in account": with the account chosen, invoicing creates the receivable already settled there, with no manual settlement in finance. Deferred terms stay open.
In the bill of materials, the shipping manifest and the price per piece, column and form field names now appear in the language you chose — before, only the list options were translated. If your company renamed a field, the name it gave still applies.
The apparel demo account opens every screen with examples that fit together: production process, fabric inspection, kits, sales reps, consignment, packing lists, gift cards, Block K, CRM and the rest. Loading the example again only fills what is missing — nothing is duplicated.
Opening, settling or cancelling a consignment or showroom sample of an item with size and color was rejected by the stock. Each line now carries the size and color, and the balance of each one adds up.
The Household forecast is now called Household cash flow and shows each month's result (what comes in minus what goes out), the running ending balance and the period total. For the current month you see what already came in and went out of the accounts next to what is still to come — every bill you pay updates the projection.
Click a month in Household cash flow to see the biggest open outflows and inflows by category and by person, with each card statement and the fixed bills. Each group opens the entries list already filtered — that is where you decide what to postpone, renegotiate or cut.
The Customer credit method now deducts the balance the store owes the customer (exchanges, returns as credit and advance payments), starting with what expires first, and the receivable for that part is created settled. A sales return can come back as customer credit, and the customer record shows the credit and records advance payments.
Finance ▸ Month's cash shows four numbers — I have today, I will receive, I will pay, I close with — and what is due in the next seven days, overdue on top. Nothing to type: it comes from the bills you already entered. Ask Tenkai "will I end the month in the black?" and it answers with the same numbers.
Supplies ▸ Garment price reads the reference's tech pack and returns cost, suggested price at the margin you want, minimum price (below it is a loss), what is left per piece and how many pieces a month pay the fixed expenses. Saves the list price on the item and keeps the history — "the fabric went up, what about my price?" now has an answer. Percentages live in Parameters (PRECO.*).
When you ship an order, each line leaves stock by the variant the customer bought (size and color), and what comes back at delivery returns to the same variant. Before, a sized item left without taking stock out.
Your plan now has a monthly allowance of Tenkai credits. Each interaction is worth credits: a question 2, a summary 5, a document 20. Under Settings ▸ AI you see how many you used, how many are left and how many credits each pack buys. Beyond the allowance Tenkai uses the wallet; with no allowance and no wallet, it warns before stopping. Ask Tenkai "how many credits do I have?".
The Help Center now has implementation guides: step-by-step playbooks by type of operation, telling which screen to fill in, in what order, where it lives in the menu and what to check before moving on. The first one is for groups with a software house and an HR consultancy. Tenkai answers from them too.
In the pocket app, Tenkai gained the calendar button with the days you talked — resume a day or delete just that one. Each answer shows where it came from (verified without AI, facts written by AI, or raw facts), and Clear now asks first, because it deletes every day.
When creating the account, choose "Family — personal finances". Sign-up asks for the person's CPF, the account gains the household screens (accounts, entries, card, recurring rules, investments, net worth and Tenkai) and the screens speak your language: "Who pays me" instead of "Customer", "Who I pay" instead of "Supplier".
Register the card with limit, closing day and due day. Each purchase enters as a card expense with its category. At closing the statement closes by itself and a payable is created in the bank account you chose. Upload the statement as OFX or sync via Open Finance.
Electricity, water, salary, rent, school: register the rule once (when, how much, from where) and Tenka creates the next period's entry by itself. For bills that vary, turn on "value by average": the next entry uses the average of the last three you actually paid.
Savings, CDB, Treasury, funds, stocks and pension with balance, deposits, withdrawals and calculated return. The Net worth screen adds accounts, investments and property and subtracts card statements and loans — and each block leads to the list the number comes from.
"How much did I spend on electricity this year?", "when does the card close?", "how much does the family have, net of debts?", "what repeats every month?". The four questions have their own tools, answer with the number and the link to the screen that proves it, and work even without an AI key.
Whoever creates the account as a family gets its own Academy trail: start with the accounts, the card is an account that closes once a month, recurrence is a rule, and the month's cash answers the question that matters. Four short lessons, in the order a household needs them.
Under Finance ▸ Household budget, type how much the household can spend in each category this month and save. Tenka measures spending by itself, shows what is left in each envelope and notifies everyone on the account when one passes 80% and when it is overspent. At the top, the month cash in household words: have, in, out, left — with the open card statement and the fixed bills that have not arrived yet included. "Copy from last month" starts the new month in one click.
Whoever creates the account as a family gets the "I spent something" screen on the phone home: the receipt photo fills in amount, date and place; you choose the category and what you paid with (account or card) and save. The same screen shows what the household has today, the open statement of each card with closing and due dates, and the envelopes of the month with what is left. Install Tenka as an app and the screen is one tap away.
The Household budget tool answers with the limit, the spending and what is left in each envelope, and with the month cash (have, in, out, left). It accepts a window ("this month", "next month", "this quarter") and a category ("on groceries"). Every answer leads to the screen of the right month.
Recurring rules, credit card, investments and net worth: the contextual help articles of these screens now have their body translated into the ten languages, not just the title. Change the language in your profile and the help changes with it — in the side panel, in the Help Center and in search.
Build the household cost center tree (Family A, Family B, the people, the cars, the properties) and every entry says who it was for. The Household budget has envelopes per person or family, the entries list filters by the center and everything under it, and Tenkai answers "how much did so-and-so spend on food last month". A shared bill, like the health plan, is posted once and split among the people.
In Finance ▸ Categorization rules, say that "gas station" is Transport for Joao car and "health plan" is Health. What comes in by the card OFX and Open Finance arrives filled in, and every expense recorded on the phone teaches a new rule. "Apply now" categorizes old entries that have no category.
On the phone, paid by card, say how many installments: a R$ 1,200 purchase in 6× becomes six R$ 200 expenses, each in its own statement. The month statement shows only that month installment, and the forecast already sees the next ones.
Mark the income tax role on categories (rent received, property tax and condo, health, education, pension, income, exempt profit) and the Family income tax screen builds, for each person, the estimated monthly tax and the annual statement for the tax return. It is an estimate — the official one is in the Federal Revenue systems.
With the Family-type centers and the owner on each account and card, Tenka compares what each family paid with what it consumed — by center and split — and suggests the transfers that clear the month. What leaves the common fund creates no debt for anyone.
Renovation reserve, trip, land down payment: say how much, by when and in which account or investment the money stays. Progress is the real balance, and Tenka shows how much to save per month to get there. Goals also appear in the Household budget.
The Household forecast screen adds, month by month, the account balances, what comes in, what goes out, the card statements by due month (with installments) and the fixed bills that have not arrived yet — and points to the first month with a negative balance, before it comes.
Three days before and on the due date, each bill to pay becomes a notice in the bell and on the phone (and on WhatsApp, if the household turns it on). The receipt photo taken in "I spent something" stays attached to the entry as proof.
Each rented property gets a contract: tenant, amount, due day, term, index (IGP-M, IPCA, INPC, IVAR or fixed) and guarantee. Each month rent is created by itself in the property center; on the anniversary Tenka suggests the adjustment by the accumulated index; and it warns when the contract ends in 60 days and when a rent is late.
Own house, land and cars go in Finance ▸ Properties and assets, and holdings in companies (the quotas, with the percentage) go in Investments. Net worth adds everything, subtracts financing and card statements, and each line leads to the screen the number comes from.
When fetching the accounts of a connection, the credit account can be linked to the registered card and the investment account to the investment — no identifier typing. The investment already receives the position the bank reported.
A family account that loads the sample data gets the whole household ready: two families in the same cash, people and a dependent, cars, rented properties with contracts, a card with an installment purchase, a split health plan, envelopes (one overspent), goals, a categorization rule, investments with a company holding and assets. Fictitious names; "Remove samples" takes everything out.
On a freshly created account, the "Load examples" button stopped with "A required field was left empty (chamado)", and sign-up no longer built the request catalog. The request type is now born complete, and both paths work.
Both buttons sent the screen without including themselves, and the action did not run — with no error message. They now run. An automatic check now blocks the same mistake on any screen.
When you create the Family account, it already comes with the household categories (with the income-tax role set on salary, rent received, health, education and property tax of the rented property) and with the "Home" center with you inside. "I spent something", the envelopes and "for whom" work from day one.
Whoever creates the account with the "Family — personal finances" line already starts on the Family plan: only the household screens in the menu, a 30-day trial and the same price as the Começar plan. The company (PJ) of someone in the household comes in as an additional company, at the standard price.
Loading the public CNPJ data now has a switch in Parameters: by default it brings only ACTIVE establishments, as it always has; turn the switch off and suspended, unfit and closed ones come in too. It is there for when a client needs to check a company that is no longer active. The search still shows only active ones by default — the rest appear when you tick the filter on the screen.
A ticket description, e-mail or customer name carrying an "order" for the AI now enters as data, never as an instruction. If the wording tries to add a link outside the source, ask for a password or send something away, the answer falls back to the raw facts, with source.
The "See amounts" mask only covered R$. It now hides dollars, euros, pesos, yen and currency codes in every Tenkai answer, e-mail and share.
Screen reader users hear "asking", "answer ready" or "not possible". Opening the chat moves focus to the field; closing returns focus to where you were; Esc closes. Answer buttons are always visible and larger.
The waiting bubble shows how long the question has been running, how long it usually takes in your account and your position in the queue. Once started, there is "Stop"; when it fails, there is "Try again" without retyping.
A new chip in the empty chat lists the subjects Tenkai can look up for your profile, by module — only what you are allowed to see. The empty Ctrl+K search suggests three questions from the current screen.
Chips, waiting messages, refusals and the wording of the answer follow the user's (or company's) language in the platform's ten languages — before, only Spanish and English had their own wording.
A badge on the bubble shows whether the answer is verified without AI, has facts plus AI wording, stayed on raw facts because the wording was discarded, or the AI was unavailable. The screen reader reads the badge before the text.
In the chat, the calendar button lists the days you talked. You can resume a day's conversation and delete only that day. The Ctrl+J and Ctrl+K shortcuts can be turned off per person, in this browser.
The Usage screen gained "What Tenkai did for you in the last 30 days": questions answered, how many had no data, ratings, response time, cost and the amount recovered by the digital employees. Ask "how much did Tenkai cost and earn me this month?".
Account administrators get a notice when the company reaches 7 days without its first customer and first receivable, and another at 30 days without movement. Each notice goes out only once.
The agents' Office shows who answers for each digital employee, which powers have been idle for 90 days and the business goal (e.g. collect within 35 days) with the measured DSO against target. Collections warns Sales about at-risk customers; Closing warns the Reconciler.
For each open receivable, the customer's history gives the likely date and the chance of paying within 7 days of due date, with the accuracy test of the last 90 days. A customer with no history gets "not measured", never a made-up number.
In Onboarding, an OFX statement or an NFS-e XML becomes a list of customers and suppliers for you to review line by line. Nothing is saved without your tick.
Ask "how does bank reconciliation work?", "what changed in the latest version?" or "is the collections agent on?": Tenkai reads the written help, the release notes and the account settings (secrets come out masked). And when the AI is unavailable, it still finds the right tool from the words of the question instead of answering "not found" for something it knows.
Before, Tenkai could freely query only 27 hand-written record types. Now every list screen with a field dictionary becomes a query: count, list, sum and ranking by any field, scoped to your company and only for those who can see the screen. Fields marked sensitive and values that look like secrets stay out. Ask "how many reports expire this month?" or "which job titles are active?".
Melhoria. Toda alteração de permissão de perfil (ver, incluir, alterar, excluir por screen) entra na auditoria de eventos com o antes e o depois, quem mudou e quando. Permissão é a configuração mais sensível da platform — mudar sem trilha era o risco invisível.
Novo. O pedido de venda passa a emitir NF-e (modelo 55) pela PlugNotas — o mesmo credenciamento da NFS-e cobre as duas notas. O item ganhou o modelo fiscal (CFOP, CST/CSOSN, origem e alíquotas, além do NCM que já existia), e sem token a emissão roda em demonstração declarada, nunca em transmissão fingida. NFC-e do PDV entra na sequência do mesmo trilho.
Uma linha colada no seu site e aparece um chat no canto da página. O visitante pergunta, e o Tenkai responde com o que a sua conta sabe: catálogo, base de conhecimento, pílulas. Quando o visitante quer falar com alguém, o chat pede nome, e-mail e telefone e abre o lead no CRM com a conversa inteira anexada — já na cadência de inbound, para o vendedor receber com a conversa lida. O Tenkai do site não enxerga nada da operação: só o que é público. E quando a pergunta é de gente, uma pessoa da sua equipe pode ASSUMIR a conversa na hora, com a transcrição à vista, e o visitante segue na mesma janela — "troca de atendente sem contexto" não existe aqui. Configure em Configurações ▸ Tenkai no site; para desligar tudo de uma vez, há a porta "Tenkai no site" na Central de Confiança.
Cada conversa de visitante é um atendimento. Cada plano traz uma cota mensal (do Trial ao Enterprise; o Enterprise Premium é ilimitado), e o placar do mês aparece no cadastro do widget. Passou da cota, o chat continua atendendo e o excedente entra na fatura do mês seguinte — o mesmo mecanismo dos documentos fiscais e pedidos: a cota existe para o grande pagar proporcional, não para travar o pequeno. Quem prefere teto fechado liga o parâmetro "Tenkai no site: travar ao estourar a cota": aí o Tenkai para de responder novos visitantes até o mês virar, mas o formulário de contato continua e o lead ainda nasce. O placar avisa quando passa de 80% da cota.
Nova tela Comercial ▸ Perfil de cliente ideal. O Tenka olha os seus clientes dos últimos 12 meses, mede margem de contrato, recorrência e pontualidade de pagamento, e monta o retrato do quartil mais rentável: quais setores, quais estados, que porte. Depois pontua cada lead de 0 a 100 pela aderência a esse retrato — a coluna "Aderência ao cliente ideal" chega à lista de leads. Não diz quem vai fechar; diz quem vale a pena fechar. O cliente grande que atrasa todo mês não entra no retrato, e isso é de propósito.
Nova tela Comercial ▸ Prospecção. Filtre por setor (CNAE), estado, município, porte, data de abertura e capital, marque as empresas e importe como leads — cada uma já chega com CNPJ, setor, porte e a aderência ao seu perfil de cliente ideal. Quem já é lead não entra duas vezes. A base é a dos dados abertos do CNPJ (a mesma das ferramentas pagas de prospecção); quando ela ainda não estiver carregada na sua instalação, a tela explica como carregar.
Quando um lead responde com interesse, o agente Vendedora manda três horários livres do link de agendamento do vendedor responsável e pede "responda com o número". O lead responde 1, 2 ou 3 e a reunião fica reservada no Agendador, com aviso ao vendedor e atividade no lead. "Não" encerra sem reservar; 48 horas em silêncio expiram a proposta. Sem link de agendamento ativo, a Vendedora só registra o interesse — crie o seu link em Comercial ▸ Agendador.
Três perguntas novas que o Tenkai passa a responder com o dado: os leads ordenados pela aderência ao cliente ideal, as empresas que existem num setor e região na base da Receita, e quantos visitantes o chat do site atendeu no período (e quantos viraram lead). Cada resposta leva à tela que a formou.
Contatos e parceiros do cliente, taxas de adquirente, agentes de IA, métricas de painel, conectores, automações, sinais de produto, equipes e membros de projeto, critérios do radar, rotinas SDCA, salas da sede virtual e perguntas agendadas: excluir deixou de ser definitivo. O registro vai para a lixeira da própria lista (menu ⋮ › Lixeira), de onde volta com um clique — ou sai de vez, se você quiser. Antes, nesses cadastros, o clique errado não tinha volta.
Quem usa o Tenka em inglês via 18/09/2026 onde esperava 09/18/2026, e em japonês lia a data ao contrário — sem nenhum aviso. Agora dia, mês, hora e o nome do dia da semana saem no formato do idioma escolhido (o seu, o da empresa ou o da conta, nessa ordem), em telas, painéis e exportações.
Sobraram, depois da onda anterior, 526 pedaços de frase cravados em português — "de", "em", "x de y", "há N dias" — que apareciam no meio de uma tela em francês ou árabe. Todos viraram frases inteiras traduzidas nos dez idiomas, inclusive o "1–10 de 100" do rodapé de 63 listas. Nenhuma tela do sistema tem mais texto fixo em português.
Em 34 campos, o "%" ou a unidade (h, dias, x) que deveriam aparecer ao lado do número não apareciam: o componente ignorava a instrução em silêncio. O mesmo valia para o ícone de 12 abas e para o rolar interno de 10 diálogos longos. Tudo passou a ser escrito do jeito que o componente entende — e agora aparece.
O texto que a plataforma guarda como DADO — estas notas, as opções de um campo de seleção, as perguntas do Pulse e o catálogo de ferramentas dos agentes — saía sempre em português, mesmo para quem escolheu outro idioma. Agora passa pela tradução da plataforma e sai no idioma do leitor; quando a tradução ainda não existe, sai no original, nunca em branco.
Em Financeiro › Renegociações, a lista passou a ser a mesma de todos os cadastros — busca, filtros no painel lateral, export do conjunto inteiro, preferências de coluna e link que guarda o recorte. Clicar num acordo abre a ficha dele: valores, parcelas, títulos originais, títulos novos e memória de cálculo, com anterior/próximo e favorito. O botão Cancelar continua onde cabe (até a assinatura) e quem já cancelava continua podendo.
Em Suprimentos › NF-e de saída, a lista passou a ser a mesma de todos os cadastros — busca por número, chave ou destinatário, filtros no painel lateral (situação, modelo, ambiente, série, emissão), export do conjunto inteiro e link que guarda o recorte. Clicar numa nota abre a ficha dela: o que falta para emitir, itens, trilha e documento, com Transmitir, Consultar situação e Cancelar no cabeçalho. O aviso de ambiente e a inutilização de faixa continuam na lista, porque são da empresa e não de uma nota.
Em CRM › Cadências, a lista passou a ser a mesma de todos os cadastros — busca, filtros (tipo, ativa), export, preferências de coluna e lixeira com Desfazer. Clicar numa cadência abre a ficha: cabeçalho e gatilho na aba Dados, a régua de passos na aba própria, com anterior/próximo e favorito. O painel de execuções (pausar, retomar, interromper, histórico) continua na lista, porque é da empresa e não de uma régua.
Em Simulação › Cenários, a lista passou a ser a mesma de todos os cadastros — busca, filtros (tipo, situação, investimento, confidencial), export, preferências de coluna e lixeira com Desfazer. Clicar num cenário abre o cockpit em página própria, com endereço para compartilhar, favorito e anterior/próximo: faixa de resultado, alavancas, sensibilidade, DRE e caixa projetados e o mês a mês. Criar um cenário e comparar até quatro continuam na lista.
As fichas de contrato de tesouraria, cotação, devolução, entrada de NF-e, expedição e pedido de venda ganharam a explicação do que fazem e de como o ciclo delas anda (o "Ajuda desta tela" abria vazio nelas). Toda tela do sistema passou a ter descrição, a pergunta que ela responde e os nomes pelos quais a equipe a chama — é o que o Tenkai usa para levar você ao lugar certo quando pergunta "onde faço isso?".
No construtor de painéis, cada card ou gráfico pode ser restrito a alguns grupos — a margem para a diretoria e o volume para a operação, no mesmo painel. Também é possível criar regras de linha por grupo ou para todos ("responsável = quem está olhando"), que valem para o painel, o Explorer, a API, o MCP e as respostas do Tenkai. Os indicadores estratégicos ganharam a aba "Quem vê".
Pergunte "receita por cliente nos últimos meses" e o Tenkai responde com a prévia dos números e um botão "Adicionar ao painel": o construtor abre com o componente pronto — fonte, métrica, eixo e tipo de gráfico escolhido pela forma da pergunta. No construtor, "Sugerir componentes" propõe o que ainda falta no painel e "Melhorar com o Tenkai" sugere título, eixo e comparação. Você continua no comando: nada é gravado até salvar, e quem vê cada componente segue as regras de acesso.
A API analítica passou a entregar os datasets (inclusive os que a sua empresa criou) em JSON ou CSV, com filtros, colunas, agrupamento e função pela URL — o Power BI e o Metabase leem direto, sem data warehouse paralelo. As regras de linha do grupo do dono da chave e a permissão de ver valores valem igual ao painel, e cada consulta fica na Auditoria. O servidor MCP ganhou as mesmas fontes para agentes de terceiros. Conexão direta ao banco continua não existindo, de propósito.
Todo dia, na hora que a empresa escolher, a plataforma grava o retrato dos datasets dos painéis publicados (a API e os agentes leem instantâneo, com a hora declarada) e o ponto do dia de cada métrica nomeada. O card passou a mostrar "média 30 dias"; o Tenkai responde "como está o MRR contra a semana passada" sem recalcular; e o alerta do card ganhou o operador Desvio, que avisa quando o número sai do normal sem você cravar o limite.
Pergunta curta vai para o modelo mais barato entre os que a sua conta habilitou; redação de documento vai para o mais forte; o resto fica no padrão — sem você configurar nada (e dá para desligar ou cravar os modelos em Parâmetros). O consumo passou a aparecer em créditos por interação (1 rota, 2 pergunta, 5 análise, 20 documento), e Configurações ▸ IA ganhou o placar "economia do roteamento": quanto a conta deixou de gastar no mês.
No painel, o botão "Receber este painel" cria a sua assinatura: e-mail ou WhatsApp, diário/semanal/mensal, na hora que você escolher. O PDF chega como você vê o painel — só o que o seu perfil enxerga, com a sua permissão de valores. E quando você pergunta ao Tenkai pelo WhatsApp algo que vira gráfico, a resposta chega com a imagem do gráfico junto do texto.
Em Configurações ▸ Acessos, cada grupo lista os componentes de painel e os indicadores restritos a ele. O painel ganhou "atualizar agora" ao lado do carimbo de hora. A API analítica aceita pagina e tamanho. O alerta por desvio do BI passou a cair na caixa de entrada dos agentes. E a regra de linha do seu grupo vale também nas perguntas ao Tenkai sobre as mesmas entidades.
Novo. Uma screen com a platform inteira: cada módulo com o que resolve, se está no seu plano e se a sua empresa o abriu nos últimos 30 dias — medido por acessos reais, não por impressão. O destaque é o que importa: módulos que você já paga e ninguém usa, com o caminho de ativação apontando para a jornada guiada. E cada módulo mostra com quem conversa, porque aqui os números nascem no mesmo banco — não há conector para falhar.
New. Every row in the grid now has a comment thread: whoever fills it in explains the assumption right there, whoever approves asks right there — and the discussion stays recorded alongside the number, instead of getting lost in a separate email. A comment can't be edited or deleted by someone else: conversation is a record, and the author can at most remove what they themselves wrote.
Novo. "Tem algo estranho nos lançamentos?" agora tem resposta: valores muito acima da faixa histórica da própria natureza e duplicidades prováveis (mesma contraparte, mesmo valor, dias próximos) — pelas regras declaradas na própria resposta, sem caixa-preta. Lançamentos intercompany marcados ficam de fora: consolidação funcionando não é anomalia.
Novo. Pergunte "quem costuma atrasar?" ou "quando esse money entra de verdade?" e o Tenka responde com o atraso mediano de cada cliente, calculado do seu próprio histórico de baixas, e a data prevista de entrada de cada título em aberto. Determinístico: nenhuma IA inventa número — a estatística sai do seu banco e o critério vem escrito na resposta. É a cobrança agindo antes do vencimento, não depois.
Novo. No menu do usuário, "Pedir ajuda desta screen" abre um chamado que já nasce sabendo de onde veio — screen e empresa preenchidas. Quem atende não começa perguntando "em que screen você estava?", e você não precisa descrever o caminho.
Novo. Frente de caixa com abertura, carrinho por item (nome ou código de barras), sangria, suprimento e fechamento com diferença declarada. O que os outros vendem como "integração com o ERP", aqui não existe: a venda É um recebimento baixado na mesma base, no mesmo segundo. Emissão de NFC-e chega junto do emissor fiscal.
Novo. Vincule o número de WhatsApp de um usuário (Configurações ▸ Canais WhatsApp) e ele passa a perguntar ao Tenka por mensagem — saldo, vencimentos, DRE — com a MESMA régua de permissão e See Values da screen. Número não vinculado recebe recusa educada e nenhum dado. Requer canal Meta conectado.
Novo. Conecte a conta bancária via Pluggy (130+ instituições, licença ITP do Banco Central) e o extrato entra na conciliação automaticamente, pelo mesmo caminho do OFX — com a mesma deduplicação e o mesmo matching por regras. Configure as credenciais em Parâmetros (PLUGGY.CLIENT_ID e PLUGGY.CLIENT_SECRET) e o vínculo no cadastro da conta bancária.
Trocar o idioma deixou de mudar só a moldura. O nome e a descrição de todas as telas e o título da ajuda de cada uma passaram a existir em inglês, espanhol (e a variante do México), francês, árabe, bengali, híndi, japonês, russo e chinês — são mais de 50 mil textos gravados. Ainda estamos traduzindo o corpo dos artigos de ajuda, então ele pode aparecer em português por enquanto: quando a tradução de um texto não existe, o sistema mostra o original em vez de deixar a tela vazia. Em Diagnóstico ▸ Cobertura de tradução você vê quanto já está pronto em cada idioma.
This very screen you are reading was the last big island of Portuguese inside the platform: the whole version history — 562 titles and 712 descriptions — existed only in Portuguese, for anyone reading in any language. Now it exists in English, Spanish (and the Mexican variant), French, Arabic, Bengali, Hindi, Japanese, Russian and Chinese as well. Switching language now changes what is written here, not just the frame around it. The same rule as always still holds: when a text's translation does not exist yet, the system shows the original instead of leaving the screen empty. Under Diagnostics ▸ Translation coverage you can see how much is already done in each language — the body of the help articles is the front that is still under way.
What was missing was the text you read BEFORE opening any screen: the six axes (Know, Get paid, Sell, Improve, Deliver, Grow), the name of each section inside them — "The funnel", "Cash", "Hours and capacity" — and the groups on the Registers page. All of that came out in Portuguese even with the language switched. Now it comes out translated into the ten languages, along with the question that opens each axis ("Where does my next customer come from?") and the line that describes it. That was 61 labels and 12 sentences. The translation path already existed and was already wired — what was missing was the content, and that was precisely the part that could not throw an error: the screen showed the original and it looked as though the translation had simply not reached that corner.
Até esta versão a coluna de SLA respondia "vencido" ou "no prazo" — e quem precisava saber se dava tempo de atender antes do almoço tinha de fazer a conta de cabeça. Agora ela mostra o tempo restante: "6h restantes", "em risco · 40min", "vencido há 3h". A conta é feita em horas de EXPEDIENTE da sua empresa, não em horas corridas: um chamado aberto sexta às 17h com prazo de 4 horas vence segunda às 11h, e não no domingo de madrugada. O horário de trabalho e os feriados saem da configuração da sua empresa, e não mais de um padrão fixo igual para todo mundo.
Havia um caso sem resposta: o cliente pede para o atendimento parar às 18h e continuar no dia seguinte, e o relógio do SLA continuava correndo a noite inteira — o prazo estourava por uma espera que o próprio cliente pediu. Agora existe Pausar no menu de ações do chamado: o relógio congela, a pausa fica registrada com hora, motivo e a pedido de quem, e ao retomar a previsão de entrega é recalculada sozinha. O cliente vê essa pausa no histórico do chamado dele, o que encerra a conversa "atrasou por culpa de quem".
Chamado é o atendimento de sustentação que o cliente abre pelo portal, com contrato e SLA por trás. Demanda é o que exige reunião e escopo. Eram a mesma lista, e quem atendia precisava filtrar na mão toda vez. Agora Chamados tem entrada própria no menu, já recortada — e continua sendo a mesma lista por dentro, então tudo que você já sabia fazer nela (exportar, filtrar, ver o resumo, editar em lote) vale igual.
O menu de três pontos de cada linha ganhou quatro ações do dia a dia: indicar o responsável, registrar a solução (o que foi feito), justificar um atraso e pausar ou retomar. A solução passa a ser exigida antes de marcar como resolvido quando o fluxo da sua empresa pedir isso — e ela sai no relatório de horas, ao lado do chamado. A justificativa de atraso entra no histórico VISÍVEL ao cliente, com data e autor.
Quando alguém trabalha à noite, no fim de semana ou em feriado, essas horas passam a ser separadas das horas normais automaticamente, na proporção exata: um atendimento das 16h às 20h conta 2 horas dentro do expediente e 2 fora. Quanto vale a hora fora do expediente é um campo do CONTRATO de cada cliente — 2 para quem negociou em dobro, 1,5 para quem negociou meia, vazio para quem cobra igual. Nada é dobrado por conta própria: sem o campo preenchido, hora fora do expediente conta como hora normal, exatamente como antes.
Horas contratadas, horas consumidas, saldo do contrato e o detalhe de cada chamado do período (abertura, resolução, SLA, horas dentro e fora do expediente e a solução registrada), em PDF ou Word. Na tela de Chamados você gera o de qualquer cliente; no portal, o próprio cliente baixa o dele quando quiser, sem pedir. É o mesmo documento e a mesma conta dos dois lados — e ele sai no idioma de quem vai ler.
Quando o cliente comentava no chamado pelo portal, o comentário aparecia assinado por outra pessoa — um usuário do sistema escolhido por acaso, às vezes de outra conta. O cadastro de comentários exigia um usuário interno, e o portal, para conseguir gravar, emprestava o primeiro que encontrasse. Agora o comentário sai em nome de quem realmente escreveu, e os que já estavam gravados com a assinatura errada foram corrigidos.
Mudança de status, troca de responsável, pausa, retomada e justificativa de atraso agora aparecem no histórico do chamado dentro do portal. Antes o cliente abria o chamado e via apenas "aberto pelo portal", sem nenhum sinal de que o trabalho estava acontecendo — e ligava para perguntar. Anotações internas da equipe continuam internas.
O formulário de abertura ficou mais direto: as categorias mostradas ao cliente passam a ser só as que você marcou como visíveis no cadastro de tipos, e o campo de cópia por e-mail virou uma opção que cada empresa liga ou desliga. A lista de chamados ganhou o filtro de 15 dias e os botões do relatório de horas. E, se o cliente abre um chamado fora do horário de atendimento, ele confirma antes — ciente de que as horas fora do expediente seguem a regra do contrato dele, e essa confirmação fica registrada no chamado.
A lista de atendimentos recentes era o bloco mais consultado do painel e vivia espremida em meia largura, ao lado dos contratos, com cada linha quebrando em duas. Passou para baixo, em largura total.
O cadastro de comentários tinha duas marcações independentes — "comentário interno" e "visível ao cliente" — e nada impedia marcar as duas ao mesmo tempo. Quando isso acontecia, uma anotação escrita para a equipe aparecia no portal do cliente, sem erro nenhum e sem que ninguém percebesse. Agora a marca de interno prevalece: marcou como interno, fica interno. Os comentários que estavam nessa situação contraditória foram corrigidos.
O campo de anexo do portal enviava os arquivos junto com o resto do formulário, e formulário grande com arquivo excede um limite do servidor que faz ele descartar tudo em silêncio: o chamado abria sem os anexos, sem nenhuma mensagem de erro. Agora cada arquivo sobe assim que você escolhe (ou arrasta), aparece numa lista com nome e tamanho, e pode ser removido antes de enviar. Arquivo recusado por segurança passa a dizer o porquê, em vez de sumir.
Ao agir sobre uma linha de qualquer lista — mudar status, atribuir responsável, pausar — a linha continuava mostrando o valor anterior até você apertar F5. O dado ia certo para o banco; era a tela que reaproveitava a página já carregada em vez de relê-la. Para quem opera, isso convida a clicar de novo achando que não pegou. Agora toda ação que atualiza a lista relê a página. Vale para todas as telas de listagem, não só para chamados.
Quando a empresa não tinha um fluxo definido para o tipo, o chamado aberto pelo portal recebia o primeiro status da lista — qualquer que fosse ele. Em empresas cujo primeiro status é de encerramento, o chamado nascia concluído: o prazo aparecia como já cumprido e o cliente não conseguia anexar arquivo. Agora o sistema procura um status de andamento e só usa um de encerramento se não existir nenhum outro — e, nesse caso, registra o aviso.
Pausar depende de existir um status que signifique "o relógio para aqui". Quem nunca criou um desses não tinha como usar o recurso — o botão existia e não levava o chamado a lugar nenhum. Agora toda conta que ainda não tinha um recebe o status "Aguardando cliente", já marcado para congelar o SLA, com a cor de espera. Ele entra no fim da sua lista de status e pode ser renomeado, reordenado ou desativado como qualquer outro; se você já tinha um status de espera configurado, nada muda para você.
O rodapé e os cartões de resumo contavam TODAS as demandas, enquanto a lista mostrava só os chamados — então a tela dizia "84" com 48 chamados na grade, e em contas com poucos chamados chegava a mostrar um total com a lista vazia. Agora os três contam a mesma coisa. Quem usa o número para cobrar fila ou medir atraso pode confiar nele de novo.
A tela do chamado dizia o título, o tipo e o prazo, mas não dizia o cliente nem a pessoa que abriu — justamente o que se procura primeiro ao pegar um chamado que não é seu. Agora os dois aparecem no topo, na Identificação. "Aberto por" é somente leitura, porque a origem é fato histórico; para trocar o cliente continue usando o campo da aba Contexto, que é o único que ajusta contrato, produto e pack junto.
A separação entre Chamados e Demandas olha a marca "É chamado" do tipo. A primeira leva reconhecia suporte, incidente e atendimento — e deixava de fora justamente "Bug" e "Erro", que são a maioria do que se abre no dia a dia. Eles entraram. Continua valendo o mesmo de sempre: a marca é sua, e dois cliques no cadastro de tipos incluem ou tiram qualquer um.
Um chamado já concluído, mas sem data de resolução gravada, aparecia na lista dizendo "vencido há 611h" — ao lado de outros concluídos dizendo "cumprido com atraso". Duas leituras opostas do mesmo estado, na mesma tela. Agora chamado fechado nunca conta tempo para frente: quando a data de resolução falta, vale a última alteração, e quando não há data nenhuma a coluna diz que não sabe, em vez de inventar um número.
São onze colunas por chamado, e em página em pé elas não cabem: o texto saía quebrado dentro da palavra ("Resoluçã/o", "Em andament/o"). O PDF passa a sair deitado, com as colunas inteiras. O arquivo Word continua igual — nele a tabela já se ajustava sozinha.