Skip to content
  • There are no suggestions because the search field is empty.

Bulk Creating Orders/Tickets

Record the orders of your customers that were transacted in bulk.

Bulk Creating Orders/Tickets

The settings under the Bulk Creating Orders/Tickets function allow you to create orders in bulk. This is usually for corporate events/free events that need to record/document orders that have already been transacted earlier, outside the HelixPay ticketing system (usually paid in cash).

 

 Configure your Bulk Creating Orders/Tickets by following these steps: 

 

1. Go to Orders > Click the the vertical ellipsis () beside the Search by field. 

  

 

2. Click “Import Orders”. 

  

 

3.  In the Import Orders interface, 

  • (Optional) Toggle on ‘Mark as paid” if you wish to record the order as paid (settled).
     Note: It will be marked as paid in cash. 
  • (Optional) Toggle on “Email Notification?” and/or “Enable SMS?” if you wish for your customer to receive a “Payment Successful” update that their order is already paid via email and/or text. 
  •  Disregard the “Enter Printer ID” field. 
  •  Note: You will also see a tabular dashboard of the Past Imports that you made.  

  


4. Click “Download Template” and select Export Type (either Export as CSV or Sign in with Google). 

  

  

 

5. You will be led to the exported Order Template. 
Note:  Data under Column F (product_id), Column G (variant_id) and Column H (seat_id) will be sourced from the Variant IDs and Seat IDs sheets, which will be tackled in the next steps.  

  

 

6. To source product_id and variant_id, click “Export Variant IDs” and select Export Type (either Export as CSV or Sign in with Google). 

  

  

 

7. You will be led to the exported Product Details list. This will serve as a reference for your imported orders.  

  

 

8. To source seat_id, click “Export Seat IDs” 

  •  Select Event and Section (from the dropdown list). 
  •  Select Export Type (either Export as CSV or Sign in with Google). 

  

  

  

  

 

9. You will be led to the exported Seat IDs list. This will serve as a reference for your imported orders.  

  

 

10. After downloading the templates, set the Email Content of the “Payment Successful” email/SMS update for your customer. 

  •  Encode the text for the Email Subject. 
  •  (Optional) Add banner image 
  • Encode the text for the header and subheader.
  • (Optional) Send a test invitation/email blast by clicking “Send test”.

  

  

 

11. After setting up the Email Content, prepare to import the Orders. 

  

 

12. Go back to the exported Order Template and prepare to encode the following details: 

  •  group_id: Label this to group certain orders under one customer (it can be a number, text, a mix of both, etc.)  
  •  name: Encode the name of your customer. 
  •  mobile number: Encode the mobile number of your customer. (For PH numbers, do not start with 0. Start with 9). 
  •  email: Encode the email address of your customer. 
  •  country_code: Encode the country code of your customer. 
    Note:  In the case of a Philippines-based customer, the country code is PH
  •  product_id: Encode the Product ID (sourced from the exported Product Details list). 
    Note: See steps below on how to do this.
  • variant_id: Encode the Variant ID (sourced from the exported Product Details list).
    Note: See steps below on how to do this.
  • seat_id: Encode the Seat ID (sourced from the exported Seat IDs list).
    Note: See steps below on how to do this.
  • (Optional) date: Encode the data of your event.
  •  (Optional) start_time: Encode the start time of your event. 
  •  (Optional) end_time: Encode the end time of your event. 
  •  quantity: Encode the quantity of the customer’s order. 
  •  (Optional) price: Encode the price of the customer’s order.  
     Note: It already has a default price based on the storefront pricing. However, you may encode it if the customer has a special pricing. 
  •  (Optional) patron_code: Encode the patron code of your customer. 
  •  (Optional) subtype_id: Encode the Subtype ID of your customer.  

  

 

13. Open your exported Product Details list, see columns C (Product ID) and D (Variant ID). Then, assign the appropriate product_id and variant_id to your customer by encoding them on your exported Order Template. 

  

 

 In this example, we’ve selected three products: 

  •  “Espresso Nights Tour [Seat Map] with a Product ID of 26153 and Variant ID of 2872322 “HelixPay Ticketing” with a Product ID of 34720 and Variant ID of 2976602, “Tote Bag Merch” with a Product ID of 37247 and Variant ID of 3004483.  
      


  • Then, we encoded them accordingly on the exported Order Template.
      

 

14. To encode the Seat ID (only for ticket orders with assigned seats), open your exported Seat IDs list. Then, assign the appropriate seat_id to your customer by encoding them on your exported Order Template.

  

 

 In this example, we’ve selected Seat B3 with Seat ID 723030. Then, we encoded it accordingly on the exported Order Template. 

  

 

15. Encode the other fields needed for your order (e.g. quantity, price). Then, place additional orders to record them as necessary. 

  

 

16. Save the Order Template as a .csv file.  

 

17. Click “Upload File” in the Import and upload the CSV file.  

  

  

 

18. Click “Import” and wait for the file to be imported successfully by checking the Status column. 

  

  

19. Your customer’s order is seen in the Orders interface on the console. 

  

20. On the end of your customer, they would receive email and SMS updates (if you activated this function).  

Sample email update: 

  

Sample SMS update: