apps.yanchi.in
Yanchi operating system
Subsystems
Each tile is a real subsystem route. We will fill these in module by module without rebuilding the shell again.
COD, merge, RTO risk, previous in-transit, bad address, ready dispatch, labels, and order decisions.
Sprint 1WarehouseScan ManagementForward scan, packing checks, pickup handover, duplicate blocking, courier mismatch, and RTO receiving.
PlannedAfter-salesReturns & ExchangesCustomer return portal, exchange requests, RTO receiving, QC, reverse pickup, and eligibility rules.
PlannedFinance opsRefundsRefund approval, payout details, UPI/bank/Shopify methods, customer status page, and refund messages.
PlannedCustomersCustomer CareTickets, calls, missed calls, WhatsApp history, order context, internal notes, and follow-up tasks.
PlannedAccountingTally & SettlementsTally exports, invoice exceptions, settlements, credit notes, payment reconciliation, and accounting batches.
PlannedCatalogueProductsProduct catalogue, SKU data, pricing, Shopify metafields, product reports, and marketplace listing hooks.
PlannedPipesIntegrationsRaw Shopify, Delhivery, WhatsApp, IVR, payment gateway, and return-system webhooks before normalization.
FoundationConfigSettingsCOD tags, courier aliases, risk thresholds, refund messages, Tally ledgers, provider topics, and safety switches.
FoundationSystemAdmin & AuditUsers, roles, permissions, audit events, job retries, settings, secrets status, and safety switches.
FoundationFoundation rules
Logic we are preserving
- Old system remains live until this OS is proven.
- Every external event is stored raw before normalization.
- Every manual or automated business action becomes an audit event.
- No label, refund, WhatsApp send, or production write happens without explicit workflow gates.
First backend target
Shopify dual webhooks
Shopify can send the same order events to the old app and this new API. Yanchi OS stores those payloads in its own clean database and computes the new Order Core read model from there.
Open Order Core