Ecommercen Docs

Appearance

Client Features Reference ​

Flow ID: SY-30 | Module(s): Platform | Complexity: Reference

Business Overview ​

The platform supports multiple client repos, each forking the base repository and adding client-specific customizations. Many platform capabilities exist in the base codebase (often gated by registry flags or disabled by default) but are only activated and proven in production by specific client deployments.

This document describes the pattern of how client features work. It is not an exhaustive inventory — the actual client ecosystem evolves continuously, and a full audit would require investigation across all client repositories.

How Client Features Work ​

Client repos extend the platform via:

  • Registry flags — features gated by registry keys (e.g., enablePoints = false in base, true in a client)
  • Controller overrides — application/controllers/ or application/modules/ replacing or extending base behavior
  • Custom directory — custom/ with PSR-4 namespace (Custom\) for modern domain/REST/job extensions
  • Config overrides — client-specific application/config/ entries

A feature is considered "proven" when it has been running in production on at least one client deployment.

Example Patterns ​

The following are representative examples of client feature categories. These are not exhaustive — many more exist across the client ecosystem.

Registry-Gated Features ​

Some features ship in the base repo but are disabled by default:

  • Loyalty Points — point accrual, spend thresholds, welcome bonuses, promotions. Gated by enablePoints and POINT_SYSTEM.* registry group.
  • Quick-View Modal — Vue-based product quick-add modal with attribute/variation selection.

Feed Customizations ​

Clients often add marketplace-specific feed controllers:

  • Color-splitting in feeds — creating separate marketplace listings per color variant with independent stock tracking
  • Marketplace-specific feeds — CSV or XML feeds tailored to specific marketplace platforms (e.g., Commerce Connector, Efood)

ERP Integrations ​

Bidirectional ERP sync is common, with patterns varying by ERP vendor:

  • Webhook-based sync — inbound webhooks from ERP systems for product/order data
  • Scheduled job suites — dozens of sync jobs covering products, persons, events, orders, statistics

Vertical-Specific Modules ​

Different verticals (pharmacy, publishing, education) add domain-specific entities:

  • Authors/Persons — author entities linked to products, common in bookstore clients
  • Product Sections — rich content sections (podcasts, videos, awards, educational materials)
  • Warehouse Scheduling — availability scheduling based on seasonal or weekly warehouse hours