How to delete Test Orders

Scroll down to the menu tab and click on 'Settings'

When a test order is deleted, a request is submitted. The deletion process may take time depending on the number of cards in the order.

If the order contains a TS Product, the request is sent to the TS Dashboard for verification of Deletion.

All orders tagged as Test Orders should be displayed under the Delete Test Order tab.

If the Test Order tag is removed from an order , it should no longer appear in the Delete Test Order tab.

Orders will be shown in the Delete Test Order tab solely based on the Test Order tag.

This filter allows the client to search for orders by entering either the Order Number or the Customer Email.

Orders matching the provided Order ID or associated with the entered Customer Email will be displayed in the results.

This filter enables the client to search for orders based on a specific date.

The client can either select a date using the calendar picker or manually enter the desired date.

Orders placed on the selected date will be displayed in the results.

This filter allows the client to search for orders based on their status using a dropdown menu.

The dropdown includes two options:

Upon selecting a status, only the matching orders will be fetched and displayed in the results.

This filter allows clients to search for orders based on the store name.

Orders will be fetched according to the store from which they were checked out (e.g., orders from Store A will be displayed when filtering by "Store A").

Clients can select multiple orders using checkboxes.

There is an option to:

Delete a single order.

Select multiple orders (up to 25 orders per action).

Use the "Select All" option to choose all orders on the page.

After selection, clients must:

Set the action to "Delete".

Click the "Apply" button to confirm deletion.

Minimum 1 order and maximum 25 orders can be deleted at a time.

25 orders will be displayed per page.

Pagination controls include:

Numbered pages (1, 2, 3, etc.) for quick navigation.

Next and Previous arrows to move between pages.

Tabs for moving forward or backward to the next or previous set of orders.

When a client selects an order and clicks the Delete button (located in the right corner, colored Red), a confirmation alert should appear.

The alert message should state:
​“Are you sure you want to delete these items?”

Two options will be available:

Cancel → If the client clicks Cancel, the selected orders remain unchanged, and any checked checkboxes should be unchecked.

OK → If the client clicks OK, the deletion process will proceed nd order Will be Deleted Shortly.

Once an order is successfully deleted, a success alert should be displayed to the client stating:
​“Your request has been submitted successfully.”

The deleted order should be completely removed from the dashboard.

If a user searches for the Card Number of a deleted order on the TS Gift Card Curate or GiveX, no results should be fetched.

If a client attempts to access a deleted order’s gift card via a direct URL, an alert message should be displayed on the screen stating:
​“Gift Card Not Found.”

If a client tests the checkout process while the store status is set to Live, all orders placed from this store will not have any tags by default.

These orders will not appear in the Delete Test Order tab.

However, it is up to the client to manually add the Test Order tags if needed.

If an order is placed from a store where the status is set to "Test," all checkout orders will automatically be tagged as Test Order by default.

These orders will also appear in the "Delete Test Order" tab for easy identification and management.

Decrease in Total Orders: The deleted order is subtracted from the total orders count of the store.

Decrease in Sales Price: The price of the deleted order is deducted from the total sales price.

If a user creates a new tag with the same name as "Test Order" and assigns it to an order, that order must appear in the Delete Test Order Tab.

Clients can delete Corporate Test Orders by selecting the relevant tags.

Navigate to the Corporate Order Tab and assign the Test Order tag to the order.

The tagged order will then appear in the Delete Test Order Tab.

Users can proceed with deleting the order successfully.

The deletion time depends on the number of cards associated with the Corporate Order.

If the order contains a large number of cards, the deletion process may take some time.

The deletion process for Complimentary Test Orders follows the same steps as Corporate Test Orders.

If a client searches for a deleted order (Corporate or Complimentary) by entering the URL directly, an alert message will be displayed:
​"Resource You Are Looking for Could Not Be Found."

(I) Reporting Excluding PII

(II) Reporting Including PII

(III) Download Reports

(IV) Corporate Order Download Report

(V) Complimentary Download Reports

(VI) Schedule Reporting

(i) Orders created via Simple Product Checkout.

(ii) Orders created via TS Monetary Checkout (Digital & Physical).

(iii) Orders created via TS Experience Checkout (Digital & Physical).

(iv) Orders created via GiveX Checkout (Digital & Physical).

(v) Orders created via Food Checkout (Delivery & Pickup).

When a user is created with the Administrator persona, all modules are automatically assigned, including the Delete Test Orders module.

The existing functionality of creating new users via CSV import remains Same.

If a sub-user is not assigned the Delete Test Order module, they will not have access to the tab.

URL Restriction: If the sub-user tries to access the Delete Test Order tab via a direct URL, an alert will be displayed stating:
​"You do not have permission to access this resource."

If a Sub-User has access to the Order Tab, they can update order tags just like the client.

If a Sub-User is assigned the Delete Test Order module, they can:

Delete Test Orders in bulk.

Delete a single order.

All functionalities related to Delete Test Order for Sub-Users remain the same as for the Client.

If an order tag is updated by the Client, and the Sub-User deletes that order, then:

All data and card details related to that order must be deleted from both the Client and Sub-User dashboards.

Neither the Client nor the Sub-User should be able to access deleted order details, card details, etc.

Master Vendors and Simple Vendors should have no access to delete a Test Order.

Master Vendors and Simple Vendors cannot delete Test Orders.

Vendors cannot update or modify order tags.

Only Clients and Sub-Users (with access) can update order tags.

When a Test Order is deleted by a Client or Sub-User, it must be removed from the Vendor Dashboard.

Vendors should not be able to access deleted orders via URL.

Order details and card details must be removed from the Download Reports tab on the Vendor Dashboard.

Deleted Test Orders must be removed from the CS Dashboard.

CS clients should not be able to access deleted orders via URL.

Note: If a Corporate Order contains a large number of cards (e.g., 100+ cards), deletion may take time nd there is a posibility of orders to be fetch in search list during that time.

Deleted Test Orders must be removed from the Fulfillment Dashboard.

Both Lead and Non-Lead Fulfillment Users should not be able to access deleted orders via URL.

Deleted Test Order data must be completely removed from Brim Reports.

If an FD User attempts to search the card balance of a Deleted Test Order, an alert should be displayed:
​“Incorrect Card Number”

Check Balance, Top-Up, Redeem and Activation actions cannot be performed on Deleted Test Order Cards by any FD User.

Store Login Users should not be able to check the balance of a Deleted Test Order TS Card.

If a Store Login User attempts to check the balance, an alert should be displayed:
​“Card Number is Incorrect”

Deleted GiveX Cards can still be checked for balance because GiveX Cards are only removed from the Client Dashboard but not deleted from the GiveX Dashboard.

Reason: GiveX operates as a third-party system, and the deletion process does not extend to their platform only Data Deletion implemented on the Client Dashboard.