Digital card inventory is not a box sitting on a shelf, but it is still subject to running out and errors. If you manage the codes yourself, you need to know which code is available, which code has been linked to an order, and which code has expired. If orders are fulfilled via a supplier, you need to know their balance, product availability, and order status on their end. Tracking both prevents you from offering a card you cannot deliver and assists you when a customer reports that a code was not received.

Do not lump all numbers together under the "Stock" field. An unsold code, a supplier's cash balance, and a paid but unfulfilled order are distinct items that require different tracking methods.

Codes in your possession or a supplier balance?

The guide to adding digital cards in Salla outlines entering codes based on country and value, including bulk file uploads under available settings. The digital cards log displays the code status, order number, date, and data that aids in searching. Check your current dashboard screens before committing to any action, especially if you are using a third-party supplier app.

How do you avoid selling a code twice?

Start at the source: do not add a single code across two import files or two different product options. Maintain separate lists for each value and country, and check the file for duplicates prior to uploading. After uploading, compare the count of accepted codes against the count you intended to add, then test a single option on mobile and track what appears in the order and log.

Hypothetical example: you have 20 codes for a single value, two of which were duplicated in the supply file. The line count is 20, but that does not equal 20 unique codes. If duplicates are not removed before uploading, you might base advertising decisions on inaccurate numbers. Keep a secure copy of source logs and invoice records, and restrict code access strictly to personnel whose roles require it. Do not place full codes in a shared file accessible to the marketing team.

If a code is used for testing or completely revealed during customer support, do not return it to the active pool, even if its status appears as "available" in an external spreadsheet. Verify its actual status and document the reason for exclusion.

A daily stock check method without extra software

Suppose you have eight codes for a single variant. Three appeared in completed orders, a fourth was used for a test, and a fifth is pending review. Do not simply say "five remaining" by subtracting only completed orders. Check the status of each individual code and its associated order: truly available stock is one thing, while an exposed test code or a pending order is entirely another. In Salla’s digital cards log, the code status, order number, date, and card details are shown, allowing you to rely on verified status rather than guesswork.

Apply a practical routine every morning: reconcile the quantity of each variant with actually available codes, review paid but unfulfilled orders, and check codes nearing expiry according to their terms. Afterward, decide whether to pause ads or restock. Do not export a file containing sensitive codes to all team members; a report showing the count of available items and orders requiring review is sufficient.

If you manage codes within the product setup, the setup guide covers minimum stock alerts and bulk uploads. Meanwhile, a supplier app balance is a separate source; do not conflate its figure with the number of codes stored directly within Salla. Check each source at its point of origin before scaling up order volumes.

When should you top up your supplier balance?

Calculate how many orders you can fulfill before sales payouts reach your bank account. Hypothetical example: your supplier balance is 500 AED, and the average fulfillment cost per order is 100 AED; theoretically, this covers only five orders, assuming no other fees or limits apply. If the balance runs out before a new payout is collected, fulfillment may halt even while store traffic continues.

Ask the supplier when the balance is deducted, when it is refunded upon a failed order, and whether cost pricing or availability changes without notice. Set a review threshold tailored to your order velocity and reload processing times, rather than copying a generic figure from another store. If you cannot confirm availability, pause ads for the affected variant until its status is clarified.

A five-minute daily check

• Reconcile paid orders against fulfilled and stalled orders.

• Review available codes by country and value, not merely by overall product totals.

• Scan for any used, exposed, or expired codes.

• Check supplier balances, pending orders, and reload timelines.

• Record the discrepancy, responsible owner, and remediation steps before scaling sales.

Once your status is clearly established, set up digital card management in your Salla store and test a single order before uploading larger batches.

A prompt to help detect inventory shortages

I manage a digital cards store.
Data for each product: [Name, Country, Value, Number of unique available codes,
Excluded codes, Paid and fulfilled orders].
Current supplier balance: [Amount], and fulfillment cost per order: [Amount].
Balance reload timeframe: [Duration or "Uncertain"].
Create a table showing what I can fulfill now and what needs review,
and list three failure scenarios that must be tested. Do not request the actual codes
and do not display them in the output. Do not treat cash balance as code count,
and do not assume supplier data syncs with the store without verification

I manage a digital cards store.
Data for each product: [Name, Country, Value, Number of unique available codes,
Excluded codes, Paid and fulfilled orders].
Current supplier balance: [Amount], and fulfillment cost per order: [Amount].
Balance reload timeframe: [Duration or "Uncertain"].
Create a table showing what I can fulfill now and what needs review,
and list three failure scenarios that must be tested. Do not request the actual codes
and do not display them in the output. Do not treat cash balance as code count,
and do not assume supplier data syncs with the store without verification

I manage a digital cards store.
Data for each product: [Name, Country, Value, Number of unique available codes,
Excluded codes, Paid and fulfilled orders].
Current supplier balance: [Amount], and fulfillment cost per order: [Amount].
Balance reload timeframe: [Duration or "Uncertain"].
Create a table showing what I can fulfill now and what needs review,
and list three failure scenarios that must be tested. Do not request the actual codes
and do not display them in the output. Do not treat cash balance as code count,
and do not assume supplier data syncs with the store without verification

Frequently Asked Questions

Is code inventory equivalent to supplier balance?

No. Codes are product items ready for delivery after verifying their status. A supplier balance is dedicated cash used to fulfill orders through them, where item costs and availability can change.

Is the total code count shown on the product page sufficient?

Check the count based on country, value, and status, then test the purchase flow. An aggregate total can mask a specific option that lacks suitable codes for the customer.

What should I do if an order is paid but no valid code is available?

Disable the affected variant from sale, review the order, the log, and the supplier, and provide the customer with a realistic follow-up timeline. Process the order in line with applicable store policies and consumer rights, then fix the root cause of the shortage before reactivating the product.

Start with a lean catalogue you can monitor effectively, then open your digital cards store on Salla. To sign up now, create your account directly.