FAQ
Questions about the TYO digital ecosystem
These answers explain how the five systems work, where responsibilities sit and how a project can move from discovery to delivery. They are written for business decision-makers evaluating a digital platform for a community, industrial park, business district or organization.
Products and ecosystem
What are the five core TYO systems?
TYOWLT is the consumer account and wallet/payment foundation. TYOBIZ manages merchant business and retail operations. TYOWORK handles workforce and organization processes. TYOLIFE provides community services and local commerce. TYOMART supports e-commerce, marketplace and defined procurement scenarios. AI is an optional supporting layer, not a sixth product.
Do we need to deploy all five systems?
No. Each system can be deployed independently where appropriate. A project can begin with the product that addresses the immediate operational problem and add connected capabilities later when there is a clear business need.
How do the systems work together?
Defined integrations can synchronize selected identities, merchant relationships and operational information. For example, a merchant relationship may connect TYOBIZ with a TYOLIFE shop, while TYOWLT payment capabilities may participate in an approved business flow. The exact integration depends on the project.
Is TYO one universal application and database?
No. The products have separate responsibilities, interfaces and data ownership. Integration does not imply one universal account, permission model or database. Each responsible system remains authoritative for the records it owns.
Accounts, merchants and employees
Are consumer, merchant, employee, dealer and supplier accounts the same?
No. They represent different business roles and retain separate ownership and permissions. Connected systems may keep a necessary local representation, but that does not merge account categories or authentication responsibilities.
How are merchants connected across the ecosystem?
TYOBIZ is the central merchant business system. Merchant identities may enter through an approved TYOWLT onboarding flow and synchronize to TYOBIZ, or be created directly in TYOBIZ for a standalone deployment. Authorized TYOBIZ merchants can be related to TYOLIFE shops.
How are merchant employees and workforce users managed?
TYOBIZ creates and manages merchant employees for merchant operations. TYOWORK maintains its own workforce and organization structures. Relevant organization relationships can be connected, while employee ownership and access remain defined by the responsible system.
Can TYOMART suppliers also be TYOBIZ merchants?
TYOMART has its own supplier account ecosystem. A supplier account can be associated with a TYOBIZ merchant relationship where the scenario requires it, but the supplier and merchant accounts, permissions and operational responsibilities remain distinct.
Integration, deployment and commercial delivery
What integration and customization options are available?
Teryo can provide a standard solution, a standard solution with integration, a partially customized solution or a fully customized engagement. Selected custom engagements may include source-code delivery where commercially agreed. Scope is confirmed through project discovery.
Does Teryo support private or on-premise deployment?
Private or controlled-environment deployment may be considered for suitable products and engagements. The exact topology, infrastructure responsibilities, providers and data controls depend on the verified product capability and the agreed project design.
Which languages and access channels are supported?
The corporate website supports English, French, Spanish, Arabic and Chinese, with Arabic displayed right to left. Product channels differ by system and deployment, and may include web, mobile and supported USSD experiences. Discovery confirms the required channels and localization scope.
How do we request a demo or begin a partnership discussion?
Use the Request Demo form or contact Teryo by email, phone or WhatsApp. Share the operating environment, target users, current systems and capabilities you want to explore. The team can then discuss product fit, integration, customization and an appropriate commercial delivery model.