A reseller catalogue needs two identities: the offer your customer buys and the provider service that fulfills it. SMM service ID mapping connects those identities. A clear mapping record helps your team change prices, review services and maintain order history without accidentally routing a customer purchase to a different product.
SMM Trust is a main SMM provider built mainly for resellers and API users. This guide explains a mapping ledger you can maintain in your own panel, database or operations sheet. The ledger is a suggested business process, not a claim that every reseller platform includes these controls automatically.
Keep retail SKUs separate from provider service IDs
Your retail SKU is your own stable reference for an offer. A provider service ID identifies an item in that provider's catalogue. They may happen to contain the same number, but they serve different purposes. A retail label can change without changing its SKU; a provider name change should not make your system create a new retail offer automatically.
The SMM Trust API reference shows a service field in the service list and uses a service ID in an order request. It also describes names, types, categories, rates, quantity limits and refill/cancel flags. Treat those fields as information to review alongside the current service description, not as permission to match products by similar names.
Use the provider and account label with the service ID in your ledger. That keeps two accounts or future provider connections from sharing an ambiguous reference. Store credentials separately; the label should identify the connection without exposing its API key.
The minimum useful mapping record
One record should explain what is connected, which version is approved and who checked it. Start with these fields, adding only what your own workflow needs:
- Retail identity: SKU, customer-facing offer name and storefront location.
- Provider identity: provider, non-secret account label and service ID.
- Service snapshot: reviewed name, type, quantity limits and source-check time with timezone.
- Commercial context: account currency, checked billing unit, cost snapshot and approved retail price.
- Input contract: accepted target format and any service-specific inputs verified from current instructions.
- Control: mapping version, effective time, reviewer and local state such as proposed, approved or paused.
Those local states belong to your system. They are not API response values. Likewise, the service-list response alone does not establish every pricing or fulfillment condition. Keep a reference to the description your reviewer used so another operator can understand the decision.
A worked example: one SKU, two mapping versions
Consider a hypothetical retail SKU VIDEO-A. Version 1 points to example provider service 4101. Later, your team considers service 5270 for new sales. These invented IDs illustrate the record only; they are not service recommendations or current SMM Trust catalogue entries.
- Keep version 1 and its effective period in the history.
- Create a proposed version 2 rather than overwriting version 1.
- Compare the service type, target requirements, quantity range, price basis and current conditions.
- Review whether the existing retail promise still describes the new service.
- Approve the new mapping with a clear effective time, or leave it paused until the differences are resolved.
Orders already submitted under version 1 retain service 4101 and their original supplier order references. Version 2 affects eligible new purchases only. A customer with an existing order should not see its history rewritten simply because the storefront now uses another service.
If an order was approved before the change but has not been dispatched, flag it for a decision. The customer approved a particular offer, and the replacement may have different inputs or conditions. A later mapping must not silently change that approved purchase.
Review changes by their effect on the retail offer
A rate or quantity limit changed
Identify every SKU linked to the service. Check the billing unit and currency before comparing costs, then review your selling price and quantity validation. Record which offers need updating. Keep already accepted quotes in a separate review list so the latest cost does not erase the original commercial decision.
The service name or type changed
A new name can be a wording edit; a different type can require another input format. Read the current instructions before approving the mapping. Matching by category or by words such as “views” is insufficient because several services can share those descriptions.
A service ID is missing from a refresh
First establish whether the latest catalogue response is complete and from the intended account. An interrupted or filtered import does not prove that a service has been removed. Pause affected new routing when necessary, investigate the source and retain historical records. Do not automatically substitute the next cheapest item with a similar name.
The existing catalogue comparison tool and review worksheet can help identify changes between saved lists. Use its output to locate mappings needing review; the report itself does not approve a replacement.
Save the chosen mapping when an order is prepared
Record the retail SKU, approved mapping version, provider account and selected service ID with each purchase. At dispatch, confirm that the approved mapping is still eligible for that order. If it is paused or superseded, hold the purchase for review rather than substituting a current value automatically.
Once the supplier returns an order ID, link it to the same record. This creates a trace from customer offer to provider order. The submission recovery workflow covers uncertain attempts; changing a mapping does not establish whether an earlier request created an order.
Make the ledger useful to the whole team
Assign one owner to approve mapping changes and another reviewer where your team size permits. Give support staff a readable history so they can answer which service an order used without editing routing. Keep a short reason for each change: for example, a quantity-limit adjustment or an explicitly approved replacement.
Before enabling new sales, check for SKUs with no approved mapping, multiple conflicting active versions, missing account labels or quantities outside the reviewed range. Revisit the affected records when a catalogue change arrives. This focused process is more useful than repeatedly approving an unchanged catalogue.
Build your reseller catalogue around clear service choices. Explore SMM Trust's wholesale services and create your reseller account. A well-maintained mapping ledger connects your commercial offers to your API workflow and gives your team a reliable history as the catalogue grows.