This week’s Zoho community activity shows a significant documentation push in Zoho Creator’s workflow engine, and a persistent undercurrent of friction in commerce, support operations, and financial tooling that signals where teams are still left to their own workarounds. One newsworthy product moment is inside Zoho CRM, where a small but telling UX improvement has arrived.
Zoho Creator’s Workflow Documentation Gets a Comprehensive Overhaul
The dominant signal in the KB feed this week is a coordinated rewrite of Zoho Creator’s workflow documentation. Approval workflows and schedule workflows each received full coverage across every action type — understanding the process, creating workflows, integration actions, data access actions, Deluge scripting, and notifications. The same pattern repeated for schedule workflows: overview, setup, actions reference, and individual articles for Deluge, data access, integrations, and notifications. The scope suggests either a forthcoming feature expansion or a recognition that the existing docs were a significant support burden. For teams building approval-heavy apps on Creator, this is the moment to audit your implementations against the newly clarified behavior — particularly the note that approval workflows do not apply to records submitted through published forms, a constraint that catches many builders off-guard.
Zoho CRM Gets Incremental but Useful UX Improvements
Two CRM updates landed this week that are worth noting together, because they both reflect an ongoing investment in daily-use polish rather than new modules. Note Reactions — emoji acknowledgments on CRM notes, with a refreshed interface that persists your formatting preference — are rolling out across data centers after launching in SA and JP. Separately, the new structured Address field has now reached all editions in all data centers including US and EU, closing out a rollout that began for IN DC users in late 2025. If your org is in US or EU and you’ve been holding off on migrating legacy address fields, the blocker is now gone — though Client Script support for the new field is still in development, so script-heavy implementations should wait.
Zoho Desk Ticket Management: Three Gaps, One Workaround Win
Zoho Desk surfaced three distinct operational pain points this week. The long-requested ability to filter tickets by read/unread status remains unimplemented and “under review” despite clear community demand — teams triaging high-volume queues are left distinguishing new responses by font weight alone. A related gap affects tickets owned by deactivated agents: there’s no native filter for them, but Zoho Support shared a useful workaround — create a Custom View using “Ticket Owner isn’t [all active agents] AND Ticket Owner is not empty” to surface orphaned tickets. On bulk operations, bulk-moving tickets between departments only works when more than 50 tickets are selected and you’re inside a specific view (not search results) — a constraint that frustrates admins dealing with mis-routed batches. One piece of good news: the Zoho Bug Tracker reauthentication option in Desk — previously requiring a full integration teardown — is now implemented, resolving a longstanding inconsistency with how the Zoho Projects integration handled credential updates.
Pricing and Commerce Complexity Is Creating Real Friction
Separate threads across CRM, Books, and Commerce this week all point to the same underlying tension: Zoho’s pricing and tax machinery is powerful but requires significant manual configuration that users keep running into unexpectedly. The CRM Pricebook thread — now over 11 years old — continues to accumulate requests for basics like a default pricebook per account, a visible pricebook selector at the quote header, and discount percentage display. None of these have shipped. In Zoho Commerce, a merchant discovered that using price lists to show VAT-inclusive prices causes the original retail value to surface unexpectedly in the storefront — a tax display interaction that isn’t well-documented. And in Zoho Books, the “Build From Scratch” HTML PDF template editor for Custom Modules is disabled by default and requires a manual enablement request to Zoho Support — even for Super Admins. Teams investing in Zoho’s finance stack should budget for these kinds of hidden activation steps and pricebook workflow gaps before go-live.
Zoho Forms Field Architecture Needs Rethinking
A single active contributor surfaced three separate Zoho Forms limitations this week that together reveal a structural issue: the field type system is too rigid. Leading zeros are silently stripped by Number fields (with the only fix being a switch to Single Line or Regex), there’s no way to mark a field as “display-only but not persisted,” forcing workarounds with hidden fields to avoid polluting the database (a “virtual field” concept), and prefix/suffix support is inconsistently available across field types (Units exist for Decimal and Number, but not Single Line or Regex). Zoho Forms acknowledged these as forwarded requests. For teams building complex data-collection workflows on Forms today, the practical takeaway is: lean on Single Line fields with custom validation over typed fields wherever you need display flexibility, and use hidden fields with Set Value rules as your persistence layer.
Zoho Billing Migration Path Remains Unclear
A new thread this week highlights a real go-live risk for businesses transitioning from Zoho Checkout: it’s not clear whether canceling Checkout will interrupt active Stripe subscriptions, or whether Zoho Billing can fully absorb those subscription relationships without a migration step. This is exactly the kind of ambiguity that causes revenue disruption. If your team is considering this transition, get explicit written confirmation from Zoho Support on subscription continuity before touching Checkout’s status.
Watch next week for whether Zoho provides formal guidance on the Checkout-to-Billing migration path — the silence there is the loudest gap in the ecosystem right now — and whether the Creator workflow documentation refresh is followed by any announcement of new workflow capabilities to match.