Release history

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.