StateSet iCommerce pricing
Choose the products your operation needs. Your monthly commitment funds one shared balance across customer outcomes, orders, warehouse fulfillments, and dispatched parcels.
Launch rate card
All rates are in USD. Final pricing and terms are confirmed in your order form. Product scope and availability are agreed individually.
| Offering | Primary billing unit | Launch rate | Monthly commitment |
|---|---|---|---|
| StateSet iCommerce CXScoped rollout | Completed customer issue, classified by outcome | $0.75 informational resolution$1.75 voice informational resolution$2.50 commerce outcome$3.00 financial outcome | $1,000/account |
| StateSet iCommerce OMSScoped rollout | Original order successfully orchestrated to the agreed fulfillment milestone | $0.10/order | $1,000/account |
| StateSet iCommerce WMSEarly access · Facility pilot | Completed fulfillment of an original order at a physical warehouse | $0.20/order per warehouse involved | $2,500/live warehouse |
| StateSet iCommerce TMS — ParcelEarly access · Scope confirmation | Parcel actually dispatched | $0.05/parcel | $500/account |
| StateSet iCommerce EDIPartner qualification | Agreed trading-partner, document-volume, and service scope | Custom quoteScope your EDI quote | Custom commitment |
| StateSet iCommerce TMS — FreightEarly access · Developer alpha | Agreed freight workflows, modes, and pilot scope | Custom quoteScope your freight quote | Custom commitment |
Scoped rollout
Scoped rollout
Early access · Facility pilot
Early access · Scope confirmation
Partner qualification
Early access · Developer alpha
Connect trading partners and exchange X12 or EDIFACT documents across the order lifecycle: purchase orders, acknowledgments, shipment notices, and invoices. Your quote accounts for live partner connections, document types and volumes, AS2/SFTP/VAN/API transport, mappings, onboarding, and the agreed support or managed-service scope.
EDI is custom quoted. Its billing meter, unit rates, commitment, and eligibility for the shared usage balance are confirmed in your proposal. EDI costs are excluded from the calculator below. Partner-specific acceptance and service responsibilities are agreed before rollout.
For a simple order orchestrated once, fulfilled at one warehouse, and dispatched in one parcel, operational software consumption is $0.35. CX applies when a separately defined customer-service outcome is delivered. Shipping and physical warehouse costs are separate.
Each enabled CX, OMS, WMS, or Parcel TMS product contributes to a single monthly dollar commitment. Eligible consumption across those products draws from the same balance.
With no opening credits
Software bill = max(commitment, consumption)
Standard terms: a 12-month agreement funded monthly, 90-day rollover of unused credits, and oldest credits used first. Negotiated discounts apply to unit rates; the monthly spending floor stays explicit. Existing agreements keep their contracted terms.
Monthly quote calculator
Start with the sample month or enter your own volumes. Adjust products, warehouse count, discounts, and credits to see the commitment, consumption, and cash due separately.
Monthly estimate · USD · Launch pricing
This calculator covers software usage for CX, OMS, WMS, and Parcel TMS. EDI, freight, and managed operations require separate scope and pricing. Review product availability or include EDI in your proposal.
Illustrative discount on all unit rates. Monthly commitments stay the same.
Balance carried into the month, before the expiry below.
Cannot exceed opening credits. Enter the amount no longer eligible for use.
Only separately scoped custom work. Standard supported onboarding is included.
Postage, freight, insurance, duties, and other third-party charges are separate from software usage.
Software cash due
$11,675.00
Includes your $5,000 monthly commitment.
The minimum is payable even in a zero-usage month. Unused credits roll over for 90 days, oldest first. This single-month estimate uses your entered expiry amount; it does not age credits automatically or model annual prepayment. Unit-rate discounts are applied before each meter total is rounded to cents. Final scope and terms are agreed in your contract.
Evaluating customer operations? Compare BPO costs with CX and retained human handling →
Usage is defined by completed business events. Attempted work, retries, and duplicate events add no consumption units. Monthly commitments fund one shared usage balance across enabled products and remain payable even at zero usage.
A distinct completed CX issue is charged once at the highest applicable outcome tier. A return and refund that resolve the same issue do not stack informational, commerce, and financial charges. Completion requires the agreed evidence; messages, retries, internal calls, and unresolved escalations add no units. The same-issue reopening window is 72 hours; a failed outcome can defer or reverse a charge.
Count an original order when it reaches the agreed orchestration milestone, such as release and acknowledgment for fulfillment. Imports, duplicate webhooks, edits, retries, and internal splits add no units. Routine orchestration uses the OMS rate; a separate customer-service intervention can be a CX outcome.
Count completed fulfillment at each physical warehouse involved. Two warehouses fulfilling an order can create two units. Multiple picks, scans, packing steps, or parcels at the same warehouse do not. Receiving, replenishment, cycle counting, automation, and multi-client 3PL requirements need agreed allowances and scope.
Count a parcel when qualifying dispatch or tender evidence is recorded. Rate shopping, label previews, reprints, voids, and unshipped labels add no units. Parcel is the scope of this rate card; LTL, truckload, and complex freight workflows are quoted separately.
Agree on supported integrations, operating limits, support, cancellations, returns, reversals, budget alerts, and overage policies before rollout. Complex B2B orders, inbound-heavy sites, automation, multi-client 3PL operations, and freight need their own scope. WMS facility and hardware acceptance still require validation; TMS is in developer alpha.
Product scope & availability
A published rate describes the commercial model. Your proposal confirms the supported workflows, connections, and acceptance required for your rollout.
Scoped rollout
Order questions, eligible returns, cancellations, and subscription changes through supported channels.
Verify customer identity, policy decisions, provider results, human handoff, and outcome records for each enabled task.
Scoped rollout
Order intake, inventory coordination, configured fulfillment routing, and exception recovery.
Confirm source-of-truth ownership, mappings, routing, fulfillment acknowledgments, and recovery from duplicates or interrupted requests.
Partner qualification
Agreed document types, mappings, transports, and trading-partner connections.
Complete partner-specific guide review, transport tests, counterparty acceptance, and downstream business validation. A connector profile is not certification.
Early access · Facility pilot
Whole-unit receiving, storage, picking, packing, and shipment handoff at a defined facility.
Local software qualification is complete. Validate the production deployment, scanners, labels, physical workflows, and integration handoffs at your facility.
Early access · Scope confirmation
A software offer metered on parcels actually dispatched. Supported carriers, label workflows, and dispatch evidence must be confirmed.
Confirm carrier coverage and demonstrate dispatch evidence, void handling, duplicate prevention, and usage reconciliation before contracting a rollout.
Early access · Developer alpha
Shipment planning, carrier tenders, dispatch, delivery evidence, and freight audit in a defined pilot.
Qualify deployment, operator workflows, identity, recovery, and production capacity. Freight rates and commitments are custom quoted.
From scope to acceptance
Every proposal should name the first workflow, supported systems, delivery responsibilities, success measures, and acceptance criteria. Timing follows the agreed scope and access requirements.
01 · Together
Agree on systems, supported actions, expected volume, source-of-truth ownership, and the business outcome to measure.
02 · StateSet configures · your team authorizes
Set up the agreed integrations, mappings, and policies. Your team supplies access, a business owner, and representative test cases.
03 · Together
Verify successful work, policy refusals, human handoffs, duplicates, timeouts, recovery, and the corresponding usage records.
04 · Named owners on both teams
Record acceptance, monitoring, escalation contacts, operating limits, rollback steps, and support responsibilities before production activation.
The CX, OMS, WMS, and Parcel TMS commitments include software access, agreed standard integrations, workflow configuration, and standard support within the signed scope. Your team operates the workflows and owns business policy.
Custom connectors, exceptional migration, managed operations, dedicated escalation coverage, and service-level commitments require a separate proposal. EDI and freight include only the services specified in their quotes. Hardware, physical warehouse work, and carrier charges are separate.
A managed-operations proposal states which software charges are included or separate and how the same work is counted. Build your rollout scope →
No. The monthly commitment funds a shared usage balance for the products you purchase. With no opening credits, your software bill is the greater of the monthly commitment and consumed service value. A $5,000 commitment covers the first $5,000 of consumption. There is no additional platform or seat-license fee.
Yes. Commitments are added together into one shared dollar balance across enabled CX, OMS, WMS, and Parcel TMS products. They are not separate product wallets. A warehouse commitment contributes to that same pool. EDI and freight credit eligibility and commitments are scoped separately.
The monthly minimum remains payable, including a zero-usage month. Unused monthly credits roll over for 90 days and are used oldest first. Unused credits can expire. Your agreement defines the credit schedule and overage policy.
Negotiated discounts reduce unit rates while the contracted monthly minimum stays unchanged. Valid opening credits plus the current monthly commitment cover usage first. Usage above that balance is additional consumption. Expired credits do not cover usage, and opening credits do not waive the new monthly commitment.
Yes, when distinct services are delivered: OMS orchestration, WMS fulfillment, and TMS dispatch. Internal calls and retries do not manufacture new orders or additional CX outcomes. Each billable record must have a business identifier, product, milestone, rate, and any reversal. One paying entity is agreed per event.
For CX, OMS, WMS, and Parcel TMS, the monthly commitment includes software access, supported onboarding, standard integrations, and standard support within agreed scope. Exceptional custom implementation uses a separate statement of work. Physical warehouse operations, hardware, carrier postage, freight, insurance, duties, taxes, and third-party costs are separate.
These are our launch rates and entry commitments. The standard agreement is 12 months, funded monthly, with 90-day credit rollover. Final pricing, availability, support, operating limits, cancellation and returns rules are agreed in writing. Existing customer contracts and negotiated annual credit pools retain their contracted terms.
Review your volumes, milestones, integrations, and rollout with the StateSet team.
Request your quote