When you are processing 10 orders a day, customer service is easy. You reply on WhatsApp, you remember every customer by name, and if something goes wrong, you fix it immediately.

When you cross 150 orders a day, that personal touch collapses. Inquiries scatter across Facebook Messenger, WhatsApp, Instagram DMs, SMS, and lost email threads. Support staff spend 80% of their time asking: "Can you please tell me your order ID?" Customers get frustrated, complaints escalate, and chargebacks or delivery refusals spike.

This week, we took on three enterprise operational bottlenecks that hit growing stores simultaneously: fragmented customer support, manual staff commission accounting, and risky payment methods.

1. The Order-Linked Customer Support Helpdesk

Traditional helpdesk plugins exist in a vacuum. A ticket is just a text thread with no context about whether the person asking spent ৳500 or ৳50,000 with you. Support reps have to open a second browser tab, search the order database, and cross-reference delivery tracking numbers.

In Manmerce, we engineered the Customer Support Helpdesk (/admin/tickets and /account/tickets) as a native first-class citizen:

  • Automatic Sequential Reference: Every ticket receives a unique traceable reference code: TKT-YYYY-XXXX.
  • Direct Relational Order Link: When customers open a ticket from their self-service dashboard, they pick the specific order from a dropdown. The agent immediately sees product photos, paid amount, courier tracking code, and delivery history right beside the conversation.
  • Private Staff-Only Internal Notes (is_internal_note): Support reps and managers can converse privately inside the ticket thread—discussing courier disputes, fraud suspicions, or replacement approvals—without the customer seeing those internal notes.
// Internal vs. Customer Message Visibility
if ($message->is_internal_note) {
    // Visible exclusively to authenticated admin staff and support agents
    $this->authorize('view-internal-notes');
}

2. Transparent Staff Commission Accounting

Every retail brand incentivizes their team. In-store cashiers earn commissions for cross-sells, and digital sales agents earn bonuses for closing orders over phone calls or WhatsApp. But almost every brand we interviewed managed commissions in an ad-hoc spreadsheet at the end of the month.

Spreadsheet accounting leads to disputes, missed payouts, and zero auditability. In Manmerce, we built the StaffCommissionService:

  • Granular Rule Engine: Set percentage or flat commission rates per staff role (sales_agent, cashier, manager), with optional minimum order thresholds and maximum payout caps.
  • Lifecycle State Machine: When an order is placed, commission is recorded as pending. Only when courier status updates to delivered (or POS receipt is closed) does it move to approved.
  • 1-Click Payout Vouchers: At the end of the pay period, managers generate official payout vouchers (PAYOUT-YYYYMM-XXXX) consolidating cleared commissions with payment references and disbursement notes.

3. Conditional Payment Gateway Rules: Protecting Margins

Payment gateways shouldn't be dumb checkboxes. Offering Cash on Delivery (COD) on a ৳30,000 custom-engraved leather jacket to an unverified buyer in a remote zone is a recipe for catastrophic return shipping losses.

We built dynamic payment gating logic directly into PaymentGateway::isAvailableForOrder():

  • Order Value Constraints: Enforce min_amount and max_amount thresholds per gateway (e.g. COD restricted to orders under ৳5,000; bank wire required for orders above ৳25,000).
  • City & District Whitelisting: Limit COD availability to courier-safe metropolitan areas while requiring upfront online prepayment for high-risk zones.
  • Anti-Fraud Score Gating: If a customer's historical courier delivery failure rate exceeds 30%, COD is automatically hidden from their checkout screen.

Next week: how we solved high-ticket and wholesale selling before checkout happens—with our B2B Quotation engine and CRM lead pipeline.

Mustafa Kamal Hossain

Mustafa Kamal Hossain

Founder & Principal Engineer at Manfi. Passionate about Laravel, SaaS architecture, and high-performance engineering.