that doens't sound like normalised data.
you are repeating 3 elements in both tables "PhoneName, SerialNo, FaceValue"
depending on how your sales work or are booked you coudl easily enough sum the quantity sold from a specific book and compare that against the quantity in the book
from what you have posted so far I'd probably look at 3 tables
one table defines details of card types (including the quantity in that card type)
details of cards on hand (eg details, date bought, serial no's etc..)
details of sales
the sold out is actaully a fucntion of the user interface, not something you actually store int he db.
however its perfectly legitimate (assuming you can justify it) to store a sold out flag in the card details. such justification could include performance or business logic... but I don't think your needs as described so far merits such a violation of normalisation
Fundamentals of Relational Database Design -- r937.com
The Relational Data Model, Normalisation and effective Database Design
I'd rather be riding on the Tiger 800 or the Norton