All Features
Cross-Platform Capability
True Multi-Channel
Unlike systems that bolt channels on later, SilverEarth Commerce seamlessly integrates them into the core from the ground up. Group related sales channels, vary commerce rules by channel, and keep fulfillment, reporting, and metadata channel aware without adding overhead when you only operate one storefront.
Channel Groups & Targeting
Organise sales channels into groups so products, events, discounts, and other shared settings can be targeted once and inherited across multiple storefronts. That keeps the admin clean when you manage many resellers or parallel channel families.
Grouped channels
Target a channel family instead of duplicating configuration for each storefront.
Shared rules
Reuse pricing, discount, and product rules while still allowing channel-specific overrides.
Managed metadata
Override page titles, descriptions, and other metadata per channel to simplify publishing.
Reseller analysis
Compare sales across channels and resellers from one reporting surface.
Available now
Website channels today
Website channels are supported now. POS, Mobile POS, and Woo-Connector channel types are in active development.
Website storefronts
Use different public sites, different metadata, and different policies where needed.
POS in progress
In active development for store terminals, tellers, and device-aware workflows.
Mobile POS
Designed for phones, tablets, laptops, and desktops with automatic geo tax mapping and use with approved peripherals.
Channel policies
Different payment, email, and shipping policies can be assigned to each channel.
Operational impact
The backend stays channel aware
- Fulfillment can branch by channel, so packaging, delivery rules, and reporting stay aligned with the storefront that sold the order.
- Configuration can vary by channel group, which makes it easier to operate branded experiences or reseller programs from one admin.
- Metadata overrides let managed pages stay centrally controlled while still allowing local differences for a specific channel.
- Different tech stacks can be used on different website channels when one frontend does not fit every use case.
- No performance penalty when you only want one sales channel; the model stays lightweight and single-channel friendly.
Examples
Separate policies
Different payment, email, and shipping rules for different channel groups.
Channel-aware reporting
Compare performance across channels, resellers, and regions without manual exports.
Flexible stacks
Use different tech stacks for different website channels as appropriate or needed by your developers.
Website and POS together
Multiple stores, tellers, and websites all living happily together with no duplication or gymnastics.