Enrollment and identity
Customer creation, lookup, sponsor selection, enroller relationships, and replicated identities connected entry into the network.
System history / Seacret Direct
Connecting commerce and distributor operations in one platform.
Recovered source directly connects Chason, Dot Designers, and later Zyel code to a custom Seacret Direct platform spanning customer commerce, distributor operations, reporting, and support.
PlatformCommerce + back office
IntegrationExigo
DesignMulti-market workflows
The context
A distributor network is more than a storefront.
A customer-facing purchase can depend on sponsor identity, enrollment status, market rules, language, pricing, shipping, recurring orders, and an external operations engine.
Behind that purchase, distributors and staff need reporting, hierarchy views, promotions, events, communications, support, and tools for operational exceptions. The recovered Seacret Direct codebase treats those concerns as parts of one connected platform.
The challenge
Keep customer experience and network operations in agreement.
Commerce rules change by market, while customer and distributor records also have to remain coordinated with the operating system behind the business.
That makes every apparently simple flow—enrollment, checkout, an auto-order, an event ticket, or a support request—part of a broader system. The platform had to carry context across public shopping, authenticated back-office work, administration, and Exigo-connected operations.
The platform
Customer, distributor, and staff workflows shared one application family.
Market-aware commerce
Culture, language, country, region, address, shipping, payment, promotion, and order branches shaped checkout behavior.
Recurring orders
Auto-order templates and item-selection workflows supported repeat purchasing inside the same customer platform.
Network reporting
Searchable binary-tree views, custom reports, and leaderboards exposed distributor hierarchy and activity.
Events and communication
Promotions, event administration, ticket purchasing, broadcasts, and culture-aware messages supported network participation.
Support and operations
Ticket workflows and management tools covered customer, order, warehouse, status, replacement, and exception handling.
The outcome
A connected operating surface existed across the network lifecycle.
The archive proves a substantial application family rather than a mockup or marketing concept.
- Customer, sponsor, shopping, checkout, and recurring-order workflows connected with Exigo operations.
- Culture, language, country, and market rules were first-class application concerns.
- Distributors could navigate hierarchy reporting and network performance surfaces.
- Staff could manage events, promotions, communications, support tickets, and operational exceptions.
Why it matters
Complex networks need one coherent operating model.
Partner, franchise, dealer, membership, and distributor businesses all become fragile when their customer journey and operating systems tell different stories.
The durable lesson is not a particular direct-selling model. It is the architecture of connected work: identity, commerce, recurring activity, reporting, communication, and support designed as one system instead of isolated projects.