E-Commerce Software Resources
Articles, Glossary Terms, Discussions, and Reports to expand your knowledge on E-Commerce Software
Resource pages are designed to give you a cross-section of information we have on specific categories. You'll find articles from our experts, feature definitions, discussions from users like you, and reports from industry data.
E-Commerce Software Articles
What Is Social Commerce, and Why We Created a New Category for It
COVID-19 Drives E-Commerce Growth for Brick and Mortar Retailers
E-Commerce Software Glossary Terms
E-Commerce Software Discussions
Running usage-based and fixed-fee pricing side by side trips up more billing platforms than vendors admit, since usage metering and flat subscription logic are built differently underneath. We compared the best Subscription Billing platforms for SaaS companies running both models at once.
These platforms come up most for this combination:
- Chargebee: Reviewers cite native support for hybrid pricing, usage-based add-ons layered on flat subscription tiers, without custom invoice logic.
- Stripe Billing: Flexible metering combined with fixed subscription items, though several reviewers say complex hybrid structures need more custom logic than Chargebee's out-of-box setup.
- Stax Bill: Mid-market SaaS reviewers cite usage-based billing alongside tiered plans, with automated proration when customers switch models.
- Gotransverse: Deep usage-metering capability for complex, high-volume scenarios, though a smaller review base suggests a narrower buyer than the others here.
- Recurly: Strong subscription lifecycle management, with usage-based billing described as newer relative to its core fixed-subscription strength.
For companies that migrated from pure fixed-fee to hybrid pricing, which of these required the least re-platforming versus just adding a new pricing configuration?
Pure subscription billing is straightforward compared with a contract that says: $20,000 platform fee, $30 per seat, then usage above a threshold. For SaaS companies running hybrid pricing, G2's Usage-Based Billing theme points to these products in particular:
- Chargebee (4.4, 996 reviews) supports multiple pricing models, as well as subscriptions, invoicing, dunning, taxes, and contract terms. The current Starter plan explicitly includes multiple pricing models. Reviewers like the flexibility, but cost becomes a recurring concern as businesses scale.
- Maxio (4.3, 831 reviews) is built specifically around B2B SaaS financial operations and appears across G2's billing, subscription management, analytics, and usage-based billing categories.
- Recurly (4.0/5, 206 reviews) handles automated subscription billing and plan management alongside payment recovery and revenue recognition. Reviewers generally like its subscription-management automation, although reporting and certain billing edge cases draw criticism.
For SaaS finance teams running hybrid pricing, which part is hardest to keep accurate: usage ingestion, proration, contract changes, or explaining the invoice to the customer?
Something none of these reviews get into is what happens mid-contract when a customer renegotiates their pricing model partway through a term. Does the billing platform actually handle that cleanly, or does it usually mean a manual workaround until the next renewal?
Enriching a catalog of a few hundred SKUs one at a time isn't realistic, so bulk import and edit tooling matters more than almost any other feature here. What reviewers in the Catalog Management category say actually speeds up enrichment:
- Akeneo PIM: Bulk attribute editing and import templates central to onboarding a large catalog quickly.
- Salsify PXM: Bulk editing tied directly to channel syndication, so an update also pushes to connected channels without a separate export step.
- Descartes Sellercloud: Marketplace-heavy sellers cite bulk listing updates across channels over manual per-channel edits.
- Etail Solutions: Bulk catalog operations tied to inventory and order data together, useful when enrichment shouldn't be separated from operations.
For catalogs in the tens of thousands of SKUs, has anyone hit a practical ceiling on bulk import size or speed with any of these?
I haven't come across a specific SKU number people point to as the ceiling, but the pattern seems to be that it's less about the import itself and more about validation, once you're at tens of thousands of SKUs, a bulk import with a bad attribute mapping doesn't just fail, it can take a real chunk of time to identify which rows caused the problem. That's probably a stronger argument for testing on a smaller batch first than for treating any of these as having a hard technical limit.





