Kanban, regardless of the method or what it looks like, is simply a mechanism to signal production of a specific part at a specific quantity. It is used to facilitate flow where it couldn't otherwise be achieved. This could be due to the inability to stabilize the cycle times of the various operations, or because the processes are not connected. Think of a customer with their supplier across town, or a milling machine supplying parts to an assembly line on the other side of a 300,000 sq. ft. manufacturing facility.
The production scenarios (from best to worst) are:
1) Flow
2) FIFO Flow
3) Kanban
4) Batch
I can't remember which book/s cited (I'd have to look it up) the practice of "single-use kanban" or "one-time kanban" but if I remember correctly there are two reasons for the use of it:
1) Repetitive orders which have either a long frequency between orders and/or a low order quantity.
2) As a necessary mechanism due to a extreme and unexpected spike in production. I have used this concept in a seasonal environment.
Either way, once the parts are produced and delivered to the required delivery point, the kanban is destroyed or removed from the process.
Wayne