Who We Are
Koriyar.com is a digital product and commercial brand operated under e People Solutions FZC. The brand exists to make delivery-related coordination easier for UAE sellers who need a modern way to create, manage, pay for, monitor, and update trips. The practical need is simple: thousands of small merchants, home businesses, social sellers, clinics, florists, bakeries, repair providers, boutiques, and service operators need a reliable operational screen between a customer request and a completed handover. Koriyar provides that screen as a software platform.
Our role is to provide a portal where order information can be submitted, normalized, priced, routed, tracked, and communicated. We provide software modules for seller onboarding, rider onboarding, wallet balances, payment links, hosted checkout where supported, route references, live tracking, proof of delivery, voice dispatch, and status history. These modules are technology services. They are part of a digital workflow, not an assertion that Koriyar itself owns vans, employs courier staff, operates a regulated courier fleet, or contracts as a carrier of goods.
e People Solutions FZC is the legal entity behind the Koriyar.com brand. The platform is positioned as an electronic portal and transaction coordination service. The owner has described the applicable licensed activity as E-transaction Complex, and the Koriyar platform is designed to fit that technology-led activity by providing online transactions, portal access, workflow automation, communications, and operational software for connected users. The platform is therefore structured as a SaaS and marketplace coordination layer rather than as a courier company.
The Problem Koriyar Solves
Small businesses often do not need a traditional courier company relationship for every order. They need a way to capture the order details, calculate a delivery fee, confirm payment, assign or notify an available service participant, show a tracking link to the customer, and record evidence that the handover occurred. Without a portal, this process becomes a collection of screenshots, voice notes, manual shipment messages, spreadsheet rows, payment links, rider calls, and customer follow-ups. That manual pattern is slow, inconsistent, and difficult to audit.
Koriyar turns that scattered process into a connected digital workflow. A seller can enter pickup and drop-off information, choose whether to pay through a trip payment link or wallet balance, receive a tracking code, and pass a public tracking link to the customer. A rider or service participant can register availability, receive trip information, update status, share live GPS, and attach proof. An operations user can review leads, tracking records, payments, wallet entries, and compliance profiles. These are software functions designed to simplify business processes.
The value of the platform is therefore not ownership of the physical movement. The value is the intelligent orchestration of information around that movement. Koriyar helps parties communicate better, reduce duplicate effort, maintain consistent status records, and create a more transparent customer experience. That is a portal function. It is similar in principle to the way many SaaS platforms coordinate transactions among independent parties without becoming the underlying regulated provider of every physical action that follows.
What We Mean by SaaS Provider
SaaS means software as a service. In Koriyar's case, the service is a browser-based and API-connected software environment that helps users manage delivery-related transactions. The seller interface lets merchants create shipments, manage wallet top-ups, and view transaction history. The rider interface lets operational participants show availability and update trip progress. The tracking interface lets customers check the status of a code. The admin interface lets authorized Koriyar operations users see records, support users, and review compliance submissions.
Because Koriyar is software, the core deliverables are digital access, data processing, workflow automation, reporting, and integration. The platform can connect to external services such as secure database, hosting, payment, dispatch, messaging, and automation service providers. These integrations are software services connected to a portal experience.
Koriyar charges, records, or coordinates fees through the portal where applicable. A seller may pay a trip-specific payment link or may use wallet balance that is topped up in advance. Those payment flows are transaction-management tools inside the software. The payment record supports access to coordination services, dispatch workflow, tracking records, and operational processing. The existence of a payment flow does not change Koriyar into a courier company; it confirms that the platform is facilitating electronic transactions among users and connected service participants.
What Koriyar Is Not
Koriyar is not a courier company in the traditional sense. Koriyar does not represent itself as a postal operator, regulated carrier, freight forwarder, cargo company, transport company, or licensed courier fleet. Koriyar does not claim that all riders are employees of e People Solutions FZC. Koriyar does not claim ownership or custody of every item shown in the portal. Koriyar does not itself physically collect packages from sellers, load goods into vehicles, drive routes, or perform handovers to customers.
Where a delivery is performed, the physical part of the service is carried out by the operational party assigned, contracted, engaged, or otherwise connected for that specific task. That party may be an independent rider, a logistics partner, a merchant's own representative, a fleet provider, a third-party delivery company, or another legally appropriate participant. Koriyar provides the technology used to coordinate and monitor the task. This distinction matters because a portal can provide information tools without becoming the legal provider of every underlying field activity.
The platform's public language is therefore being aligned around software, portal, workflow, marketplace, and coordination concepts. Where the word delivery appears, it describes the business process being coordinated by software, not a representation that Koriyar itself is the regulated courier. For example, a public tracking page may say a delivery is on the way because the tracking record represents a trip status. That status belongs to the operational workflow, not to an admission that Koriyar is physically transporting the goods.
Why the Portal Activity Is Central
The license activity described by the business owner as E-transaction Complex is relevant because Koriyar is designed around electronic interactions. The platform receives electronic submissions, validates data fields, creates electronic records, generates tracking codes, presents electronic payment options, manages wallet entries, sends or receives webhook events, stores compliance profile metadata, and displays live information through a web portal. The essential activity is the handling of digital transactions and portal workflows.
A seller who uses Koriyar is primarily interacting with a portal. The seller provides order information, reviews price or wallet status, initiates a payment or wallet debit, and receives a tracking link. A rider who uses Koriyar is primarily interacting with a portal. The rider provides availability, receives trip information, and updates the status of the assignment through buttons and GPS. A customer who uses Koriyar is primarily interacting with a portal. The customer enters or opens a tracking code and sees the recorded status.
This is why Koriyar's legal positioning is closer to a transaction technology platform than a courier operator. The platform's obligation is to provide software availability, data handling, workflow records, access controls, reasonable security measures, and clear user flows. The platform may coordinate the interaction between parties, but coordination is not the same thing as physical carriage. The E-transaction Complex description supports the idea that the business activity is online transaction enablement, portal access, and digital process management.
How the Platform Works
Koriyar begins with structured intake. A seller enters the seller name, phone number, pickup area, drop-off area, items, number of stops, and preferred payment method. The platform can estimate distance, record an amount, create a tracking code, and save a tracking row. If the seller chooses a payment link, the shipment is held until payment is confirmed. If the seller chooses wallet payment and balance is sufficient, the platform records a wallet debit and clears the workflow for dispatch or assignment.
Once payment or wallet status permits progression, Koriyar can search available rider records, create or update tracking status, and trigger an automated communication through an integrated voice provider where configured. The rider side can then update pickup, on-the-way, delivered, GPS, and proof-of-delivery fields. The customer tracker displays the latest status from the database. Every one of these steps is a data and communication event. The software helps the parties know what is happening, when it happened, and what should happen next.
Payment handling is also part of the portal. Koriyar can create wallet top-up links, record wallet credits, record wallet debits, generate trip-specific payment links, and listen for payment webhook events. These functions are not a physical delivery service. They are electronic transaction functions. They help ensure that the commercial workflow is clear before the operational workflow continues. That is exactly the kind of feature a SaaS portal is expected to provide when coordinating activities among multiple parties.
Seller Responsibilities
Sellers using Koriyar should provide accurate information. That includes pickup location, drop-off location, item description, contact number, delivery instruction, payment status, and any special handling note. Sellers are responsible for ensuring that their goods may legally be sold, transported, handed over, and received in the UAE. Sellers should not use the portal for prohibited, restricted, unsafe, counterfeit, illegal, hazardous, or otherwise non-compliant goods. Koriyar's software can record information, but it cannot transform an unlawful item into a lawful one.
Sellers should also maintain appropriate business documentation where required. This may include a trade license, VAT registration or TRN where applicable, authorized person information, pickup address, and other compliance details. The platform may request these details to support onboarding and review. The request for compliance information is not a declaration that Koriyar regulates the seller's business. It is a reasonable SaaS platform control designed to reduce abuse, maintain trust, and support responsible marketplace access.
When a seller uses wallet or trip payment features, the seller should understand that payment enables the software workflow and related coordination process. Wallet balance is a convenience feature for repeated use. Trip payment links are useful for occasional or single-order usage. The seller remains responsible for confirming the commercial arrangement with their customer, packaging items correctly, and ensuring the handover instructions are accurate.
Rider and Operational Participant Responsibilities
Riders and operational participants using Koriyar should submit accurate profile information, including phone number, name, license details, vehicle information, insurance information where applicable, and identity-related details requested by the platform. These details help Koriyar maintain a safer and more accountable software environment. They also help operations users decide whether a participant should be permitted to receive assignments through the portal.
Operational participants are responsible for complying with applicable road, licensing, insurance, safety, and municipal requirements. Koriyar's software may request a UAE driving license number, vehicle plate, registration expiry, insurance expiry, Emirates ID last four digits, and supporting documents. These fields support compliance review and auditability. The platform does not replace government licensing, traffic laws, insurance requirements, or any third-party contractual obligations.
When a rider updates a tracking status, shares GPS, or uploads proof of delivery, the rider is creating a digital record inside the portal. That record helps the seller and customer see progress. The accuracy of that record matters. Riders should only mark pickup when pickup has occurred, only mark delivered when delivery has occurred, and only upload proof that relates to the correct trip. The software is built for transparency, but it relies on users giving truthful inputs.
Customer Experience
Customers interact with Koriyar primarily through tracking. A customer may receive a tracking code or link from a seller. By opening the link, the customer can see the stage of the workflow, rider location if available, ETA if available, and proof-of-delivery information when added. The tracking page is a customer-facing window into the data recorded by the platform. It helps reduce uncertainty and repeated follow-up messages.
Customers should understand that Koriyar's tracking page is an information service. It reports the status of a workflow managed through the portal. It does not by itself create a separate courier contract between Koriyar and the customer. The seller remains the customer's primary commercial point of contact for product quality, order terms, refund questions, and item-specific issues unless a different arrangement is clearly stated in writing.
The tracking experience is designed to be simple and transparent. The goal is to give customers enough visibility to know whether a trip is pending pickup, picked up, on the way, delivered, cancelled, or otherwise updated. The platform can improve the customer experience even where the physical handover is performed by an independent participant, because visibility is a digital service in its own right.
Technology and Automation
Koriyar uses automation to reduce manual work. The platform may use geocoding to interpret addresses, payment APIs to create links, database functions to update tracking, voice APIs to contact riders, webhook handlers to record events, and GPS browser capabilities to update live locations. These features are technical services provided by the portal. They are intended to make the workflow faster, easier to audit, and more consistent.
Automation does not remove human responsibility. Sellers must still enter correct information. Riders must still comply with road and safety obligations. Operations users must still review exceptions. Customers must still use the tracking information reasonably. Koriyar's automation is a tool for coordination, not a substitute for lawful conduct by the parties who use or participate in the platform.
Artificial intelligence and automated dispatch may help prioritize, route, call, or classify tasks. The use of AI does not change the legal nature of the platform. It remains a software system used to process electronic transactions and workflow records. AI helps the portal perform its digital role more efficiently, but it does not turn the portal into a physical courier operator.
Payments, Wallets, and Transaction Records
Koriyar supports two primary payment paths. First, a seller can use a payment link for a specific shipment. The seller pays for that shipment, and the portal can then move the workflow forward after payment confirmation. Second, a seller can maintain a wallet balance. If the wallet has sufficient balance, the seller can proceed with the shipment and the platform records a wallet debit. If the wallet does not have sufficient balance, the seller can top up through fixed or custom amounts.
Wallets and payment links are electronic transaction features. They help sellers avoid repeated manual transfers and help operations users see whether a workflow is financially cleared. The payment record may include provider status, amount, tracking code, wallet balance, checkout ID, payment URL, webhook status, and timestamp. These are data records. They support the SaaS platform's coordination service.
Where VAT or tax treatment applies, Koriyar may request or record business tax information such as TRN for VAT-registered sellers. The platform's ability to record TRN or show payment history is a business software function. Sellers should consult their own tax advisors for their business accounting obligations. Koriyar can provide records generated through the portal, but users remain responsible for their own tax filings and accounting treatment.
Compliance and Documentation
Koriyar may request documentation from sellers and riders before allowing full use of the platform. For sellers, documentation may include trade license information, authorized person details, VAT/TRN status where applicable, pickup address, and bank information metadata. For riders, documentation may include Emirates ID information, driving license information, vehicle registration, vehicle plate, and insurance information. These fields are designed to support onboarding review and responsible platform access.
The purpose of documentation is to protect the platform and its users. A digital marketplace or portal that coordinates real-world tasks should know who is using it. Documentation helps reduce fraud, misuse, false identities, and operational confusion. It also helps Koriyar maintain a record that it is acting as a responsible portal provider, not as an anonymous message board where unverified parties can create delivery-like tasks without accountability.
Koriyar's document handling is being structured for security. The platform is designed to avoid storing raw uploaded identity documents directly in ordinary lead payloads. Instead, document data is processed server-side, encrypted, and prepared for private storage with restricted admin access. Signed access links can be used for limited review once private storage credentials are fully configured. This approach supports the SaaS portal role while respecting the sensitivity of identity and business documents.
Why This Model Is Legitimate for a Registered Technology Business
A registered technology business can lawfully provide software tools that coordinate activity among users, provided the business remains clear about what it does and does not do. e People Solutions FZC operates Koriyar.com as a brand for digital portal services. The platform activity described as E-transaction Complex supports the provision of electronic transaction infrastructure, online workflow tools, and portal-based coordination. Koriyar's features are built around those concepts.
The important legal distinction is between providing a portal and performing the underlying regulated field service. A booking platform can connect parties without owning the hotel. A payment platform can process payment without selling the goods. A marketplace can list service providers without employing every provider. A workflow system can coordinate delivery-related tasks without itself being a courier. Koriyar follows this technology-platform logic.
Koriyar's public statements, terms, onboarding flows, and internal controls should continue to reflect this structure. The brand should avoid representing itself as a courier company. It should describe itself as a SaaS portal, transaction platform, coordination layer, and workflow automation system. It should disclose that physical services are performed by independent or third-party participants. It should require users to provide accurate information and comply with applicable law. This is the cleanest way to align the product with the legal entity's portal activity.
Our Commitment to Responsible Operation
Koriyar is being built with operational responsibility in mind. The platform includes seller onboarding, rider onboarding, wallet records, payment logs, tracking records, proof of delivery, admin review, and document metadata. These controls are not just technical features. They are part of a responsible portal design. They make it easier to investigate disputes, support users, improve routing, detect misuse, and maintain accurate records.
We also recognize that the UAE is a serious business environment with expectations around licensing, consumer trust, payments, identity, and data protection. Koriyar aims to operate in a way that respects those expectations. The platform should be transparent about the legal entity behind the brand. It should not blur the line between software coordination and physical courier activity. It should collect only the information needed for legitimate onboarding and operations. It should protect sensitive documents and restrict access to authorized personnel.
As the product grows, Koriyar may integrate more official identity, payment, communications, and business verification services. UAE PASS integration is one example of a future enhancement that can support identity verification when service-provider credentials are approved. Additional payment, messaging, and compliance services may also be added. Those integrations will strengthen the portal role by making electronic transactions more reliable and better verified.
How to Read Koriyar's Marketing Language
Koriyar's website may use simple phrases such as create shipment, track delivery, rider update, dispatch, route, proof of delivery, pickup, and drop-off. These phrases describe the workflow that users understand. They are not intended to override the legal nature of the platform. In context, these words refer to digital records and coordination steps inside a SaaS portal. They help users navigate the product without needing legal terminology on every button.
For example, when a seller clicks create shipment, the platform creates a tracking record and payment workflow. When a rider clicks picked up, the platform records a status update. When a customer opens a tracking page, the platform displays the status stored in the database. These are software events. The underlying physical handover, if any, is performed by the operational participant responsible for that trip.
This page provides the deeper explanation behind that everyday language. It confirms that Koriyar.com is a brand of e People Solutions FZC, that the product is a portal and SaaS system, that the applicable activity is being treated as E-transaction Complex as described by the business owner, and that Koriyar is not positioning itself as a courier company. That explanation should guide how users, partners, and internal teams understand the platform.
Practical Example
Imagine a home bakery in Dubai that receives an order through Instagram. The bakery needs the cake collected and handed to a customer. Without Koriyar, the bakery might call several riders, send manual location pins, create a payment link separately, and message the customer repeatedly. With Koriyar, the bakery can enter the order into the portal, pay by wallet or link, get a tracking code, and share the tracking link. A rider or service participant can update the status, and the customer can monitor progress.
In that example, Koriyar is not baking the cake, selling the cake, driving the vehicle, or physically handing over the package. Koriyar is providing the electronic transaction and coordination environment. The seller remains responsible for the product and customer relationship. The operational participant remains responsible for lawful and safe performance of the physical task. Koriyar provides the technology that connects the steps and records what happened.
This is the clearest practical expression of the platform's role. Koriyar improves coordination without claiming to be every party in the transaction. It gives sellers like you access to tools that larger businesses often have: tracking, routing, payment control, wallet management, proof records, and operational dashboards. That is the service e People Solutions FZC is providing through the Koriyar.com brand.
Conclusion
Koriyar.com exists to modernize the way UAE sellers coordinate delivery-related workflows. It is a brand of e People Solutions FZC, built around portal access, electronic transactions, SaaS automation, operational dashboards, tracking, wallet payments, and connected communications. Its model is not to operate as a courier company. Its model is to provide the software layer that helps merchants, customers, riders, and operations users interact more clearly.
This distinction is important for trust. Sellers should know who provides the portal. Riders should know what role the platform plays. Customers should know that tracking is a digital visibility service. Partners should know that Koriyar's activity is technology-led. Regulators and compliance reviewers should see that the product is intentionally structured around portal and electronic transaction services, not around unlicensed courier claims.
Koriyar will continue improving its systems, controls, documentation, and integrations. The platform will keep evolving, but the foundation remains the same: Koriyar.com is a software and electronic transaction portal brand of e People Solutions FZC, designed to coordinate delivery-related workflows while respecting the legal distinction between SaaS platform services and physical courier operations.