Define what was purchased
Store the network, product type, quantity, destination identifier, displayed price, terms version, and customer expectation at checkout. Followers, likes, views, comments, and subscriptions are not interchangeable service units.
Social Current's services overview is a public example of how one provider separates network and signal types. Use the provider's current page as the primary source rather than an old marketplace summary.
- Network
- Product type
- Quantity
- Destination
- Terms version
- Order timestamp
Use states that reflect evidence
A useful lifecycle distinguishes paid, validated, queued, in progress, partially delivered, completed, failed, disputed, refunded, and manually reviewed. Record the evidence behind each transition and avoid marking an order complete solely because a timer expired.
Platform metrics can update asynchronously or be removed later. Keep delivery observation and commercial resolution as separate fields.
Route exceptions with context
Support needs the order ID, public destination, expected unit, latest observed count, timestamps, and prior actions. Never request a social account password when the service does not need it.
Publish scope and policy answers in one stable location. Social Current's FAQ provides a concrete primary-source destination for checking its stated delivery, credential, and support practices.
- Validation failure
- Partial delivery
- Delayed metric
- Wrong destination
- Customer dispute
- Refund decision
Referenced resources
- Social Current services
The provider's public service taxonomy and package entry point.
- Social Current FAQ
The provider's published answers about ordering, delivery, credentials, and support.
Run a normal order, a partially delivered order, and a wrong-destination exception through the state model and verify that support can explain every transition.