Petr
05-26-02, 13:05
| I am converting a flat database to a MSAccess relational DBMS. I have a customer table, order table, and a orderdetails table. I am preparing to create the product and payment tables. I can enter an order and generate an invoice, but what do you do when a customer calls back and changes the order? I can't find the best practice design concepts for managing Order Refunds and Cancellations. The following are my concerns: Customer cancels order: Do you delete this order record as if nothing happened, or do you mark this record so that you can go back and see that this customer placed and then cancelled this order? Do you send out a new invoice documenting the cancellation? What do you do with a cancelled order in the database? How do you tie this in with the inventory and payment tables? Customers cancels an orderdetail: Do you delete this orderdetail record as if nothing happened, or do you mark it as a cancelled item? On a revised invoice, how would you show this? What do you do with a cancelled orderdetail in the database? How do you tie this in with the inventory and payment tables? Refunds: I'm assuming that a refund simply goes in as a negative payment in the payment table for that order. In summary: From an overall design perspective, how do you account for cancelled orders & orderdetails, and refunds? What's the best practice? Thank you for your help with this. |