Proposed merchant & rider rules
Discussion draft · Pending merchant and rider agreement · Not in effect
This is prelaunch information. Customer rules describe the planned service; the app, ordering, payments and automated workflows are not live on this website.
Pending merchant/rider agreement and legal review. Amounts, percentages and thresholds are provisional. No acceptance, debt or automatic deduction is created by this page.
Draft status: please read first
Published 30 September 2026. Reading this draft is not acceptance. Merchant and rider agreement, legal review and operational checks are required before any proposal takes effect.
Customer refunds remain separate
The planned customer refund rules remain separate from these proposed partner arrangements. A customer’s eligible refund does not wait for a merchant or rider to pay Biteway. Disputes or unsuccessful recovery do not reduce the customer’s refund. Payment and refund processing fees are not deducted from the customer’s refund; allocation of those fees between Biteway and merchants is still undecided.
Proposed rider model and delivery pay
The proposed service uses student riders, who may carry multiple orders within safe capacity. Provisional normal pay per completed delivery: MMU Hostel RM1.49; Ixora Apartment RM0.99. Under the proposal, eligible Biteway+ free-delivery orders still pay the rider the full normal delivery amount. A customer’s free delivery does not mean unpaid rider work. Eligibility, employment or contractor classification, safety requirements, per-trip capacity, payment conditions and settlement schedules still require agreement and review.
Proposed merchant confirmation and preparation duties
For ordinary orders, the intended workflow requires both merchant stock confirmation and rider acceptance before preparation. The proposed merchant arrangement is to provide an estimated preparation duration visible to the customer and rider, measured from completion of both confirmations. An accepted rider is to be told to travel only after stock confirmation. These partner duties require agreement; the app workflow and notifications are not yet active.
Proposed overdue-preparation workflow
The intended platform workflow detects an exceeded ready time immediately, reminds the merchant and asks for a revised estimate. If the merchant does not respond within a proposed 5 minutes after that reminder, the issue goes to the Biteway operating lead. Missing the revised estimate prompts immediate intervention, with the customer able to keep waiting or cancel under the customer rules. These are planned operating requirements, not a claim of live monitoring, round-the-clock staffing or guaranteed response time. A dedicated merchant messaging channel and its integrations have not been set up.
Proposed merchant responsibility for stockout and repeated delay
If a merchant confirms stock and later cannot provide it, the proposed arrangement places the resulting verified merchant-caused food loss with the merchant, including where preparation of other items has already begun and the customer chooses an eligible whole-order cancellation. The same proposed responsibility applies to merchant-caused repeated preparation delay that leads to an eligible cancellation. Causation, recoverable costs, settlement and dispute handling must be agreed and reviewed; this page does not establish a merchant debt.
Proposed wasted-trip payment
Where stock was confirmed, the rider accepted and actually reached the restaurant, and the merchant then reports stockout, the proposal is for the merchant to pay the rider a wasted-trip amount. It also covers a merchant missing its revised ready time, the customer cancelling and an already-arrived rider’s trip being wasted. Provisional amount: MMU Hostel RM1.49; Ixora Apartment RM0.99. There is no duplicate wasted-trip payment for a normally completed delivery. Arrival, cause and actual circumstances must be checked. Payment responsibility and collection remain subject to merchant agreement and lawful procedures.
Proposed wrong-food and redelivery costs
The proposed responsibility follows the verified cause: merchant mispacking would place the relevant remake or redelivery cost with the merchant; rider misdelivery would place the resulting redelivery cost with the rider, subject to lawful agreement and recovery. A merchant’s correct handoff and normal settlement should be distinguished from a later delivery mistake. The customer may still choose the applicable refund or consent to free redelivery. No forced substitute, duplicate compensation or automatic deduction from rider earnings is created by this proposal.
Proposed non-malicious accidental food-loss split
Provisional allocation: Biteway/platform 60%; rider 40%. This proposal concerns non-malicious accidents such as a fall or accidental food damage. It is not a blanket rule for merchant stockout, all delays or deliberate misconduct. The base is verified actual loss, without a punitive fine and without counting the same economic loss twice through both a customer refund and merchant settlement. Exact cost components, any recoverable value and accounting remain to be agreed. Example only: RM20 of verified actual loss would allocate RM12 to Biteway and RM8 to the rider. This example is not a bill or an automatic debt. Facts, responsibility, legal classification, lawful agreement and recoverability must be assessed first; Biteway cannot assume the proposed rider share will be recovered.
Repayment, disputes and no automatic earnings deductions
No automatic deduction from current or future rider earnings is authorised. The proposed approach is to verify evidence and actual loss, give the affected person a chance to explain or dispute responsibility, and discuss separate voluntary repayment through a lawful process where appropriate. There is no automatic instalment or collection scheme. Signing a contract alone must not be treated as permission for every deduction or penalty. Any deduction would require a separately verified lawful basis and every applicable approval and procedure. Punitive fines must not be disguised as earnings adjustments. A disputed debt does not itself trigger an automatic ban, and recovery is not guaranteed.
Proposed conduct thresholds: subject to fair and lawful process
These are provisional proposals, not an automatic penalty schedule. For a verified acceptance followed by unjustified failure to collect: first occurrence, a warning; second occurrence, a proposed 7-day suspension; third occurrence, proposed termination of the working relationship. Verified deliberate eating or discarding of a customer’s food would also be considered for termination. Merchant stockout, food not being ready or a verified reasonable accident must not be mechanically counted as unjustified failure. Before any suspension or termination, the facts, lawful grounds and applicable process must be reviewed, including required notice, investigation, opportunity to explain, reasons for a decision, and a review or appeal route. Counting periods, appeal deadlines and detailed procedures remain unsettled. No automatic fine, immediate ban or waiver of statutory rights is established here.
Proposed Drop preparation and rider-capacity arrangements
Drop remains fixed-price advance ordering for a scheduled delivery slot. The proposed operating gate requires enough confirmed rider capacity for the orders before merchant preparation, followed by batch delivery. One rider accepting does not establish sufficient capacity for an entire Drop. Per-rider load limits, rider-count formulas, assignment deadlines and a fallback for insufficient capacity are still to be agreed; no numbers are being filled in provisionally. The ordinary-order payment-plus-10-minute confirmation deadline must not be applied to scheduled Drop.
Delivery evidence and safe handoff
The proposed operating records support collection-code handoff or the customer’s expressly chosen unattended delivery arrangement. Any five-minute fallback requires advance consent to a specific safe location, actual arrival and notification before timing, an attempt to contact the customer, the full wait, and a photo plus notification after placement. Without a safe agreed place, the issue should go to support rather than arbitrary abandonment. Photos are evidence, not conclusive proof or blanket immunity. Technical records, privacy safeguards and support arrangements still require implementation.
Items still open for negotiation and review
Open items include merchant and rider acceptance; legal relationship classification and eligibility; pay and settlement conditions; the precise actual-loss calculation; evidence and dispute procedures; lawful suspension, termination and appeal steps; payment-provider fees and refund timing; internal fee allocation; rounding and replacement-price calculations; Drop capacity and failed-assignment handling; and staffed escalation arrangements. No missing fee, amount, deadline or capacity is invented by this draft. Operational integrations must be built and tested before being described as available.
Before any proposal takes effect
Biteway must review the proposals with the relevant merchants and riders, complete the necessary legal and operational checks, clearly communicate the final version and obtain any required agreement before implementation. Material changes to amounts or responsibilities must be made clear before applicable acceptance; this draft does not create a right to alter signed obligations unilaterally. Applicable consumer and worker rights remain. For questions about this draft, email support@biteway.my. This is a prelaunch enquiry address, not a promise of currently staffed order support.