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. And if orders are fulfilled via a supplier, you need to know their balance, product availability, and order status with them. Tracking both prevents you from offering a card you cannot deliver, and helps you when a customer says their code hasn't arrived.

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

Codes on Hand or Balance with the Supplier?

The guide to adding cards in Salla explains entering codes according to 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. Review your current account dashboard before relying on any procedure, especially if you use an external supplier app.

How to Avoid Selling a Code Twice?

Start from the source: do not add a single code to two import files or two different options. Keep a separate list for each value and country, and check for duplicates in the file before uploading. After uploading, compare the number of accepted codes with the number you intended to add, then test a single option from a mobile phone and follow what appears in the order and log.

Hypothetical example: You have 20 codes of a single value, two of which were duplicated in the supply file. The number of rows is 20, but that does not mean 20 unique codes. If you do not remove duplicates before adding, you might base an advertising decision on an incorrect figure. Keep a secure copy of the source log and invoice numbers, and restrict access to codes strictly to those who need it for their work. Do not place full codes in a file shared with the marketing team.

If a code is used for testing or fully revealed during customer support, do not return it to the sales list even if its status appears as "available" in an external file. Review its actual status and document the reason for exclusion.

A Daily Inventory Method That Needs No Extra System

Suppose you have eight codes for a single option. Three appeared in completed orders, a fourth was used in a test, and a fifth order is stuck in review. Do not assume "five remaining" solely by subtracting completed orders. Review the status of each code and its linked order: genuinely available codes are one thing, while codes exposed in testing or pending orders are another. In the digital cards log in Salla, the code status, order number, date, and card details are shown, allowing you to check actual statuses instead of guessing.

Apply a practical routine every morning: reconcile the quantity of each option against genuinely available codes, review paid unfulfilled orders, and check codes nearing expiration based on their terms. Then decide whether to pause advertising or replenish supply. Do not export a file containing secret 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, the adding guide outlines minimum stock alerts and uploading multiple codes. As for the supplier app balance, it is a separate source; do not conflate its counter with the number of codes stored inside Salla. Review each source in its proper place before scaling up order volumes.

When Should You Recharge the Supplier Balance?

Calculate how many orders you can fulfill before sales proceeds reach your account. Hypothetical example: The supplier balance is SAR 500, and the average fulfillment cost per order is SAR 100; theoretically, this covers only five orders assuming no additional fees or limits. If the balance runs out before settling a new payout, fulfillment might halt despite ongoing traffic.

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

A 5-Minute Daily Review

• Reconcile paid orders against fulfilled and stalled orders.

• Review available codes by country and value, not just total product count.

• Check for any code that is used, exposed, or expired.

• Verify supplier balance, pending orders, and recharge timelines.

• Log discrepancies, responsible owners, and corrective actions before scaling sales.

Once your status is clear, set up card management in your Salla store and test a single order before uploading larger quantities.

A Prompt to Help You 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 order fulfillment cost: [Amount].
Balance recharge duration: [Time 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 ask for the codes
themselves and do not display them in the response. Do not treat cash balance
as code counts, 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 order fulfillment cost: [Amount].
Balance recharge duration: [Time 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 ask for the codes
themselves and do not display them in the response. Do not treat cash balance
as code counts, 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 order fulfillment cost: [Amount].
Balance recharge duration: [Time 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 ask for the codes
themselves and do not display them in the response. Do not treat cash balance
as code counts, 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 serials ready for sale after verifying their status. Supplier balance is funds designated for fulfilling orders through them, and product costs and availability may fluctuate.

Is the number of codes displayed under the product sufficient?

Review the count by country, value, and status, then test the purchasing journey. The overall total might conceal an option that lacks appropriate codes for the customer.

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

Disable sales for the affected option, review the order, log, and supplier, and update the customer with a realistic follow-up timeline. Process the order in line with applicable policies and rights, then resolve the shortage cause before re-enabling the product.

Start with a small selection you can track, then open your card store on Salla. To sign up now, create your account directly.