SANDSTAR
Technical Support
Standard Operating Procedure
Technician & AI Support Agent Reference Guide
| Document Owner | Sandstar Support Team |
| Version | 1.4 |
| Classification | Internal Use Only |
| Support Email | support@sandstar.com |
CONFIDENTIAL — FOR INTERNAL USE ONLY
| INTRO | Purpose & Scope |
1. Purpose & Scope
This Standard Operating Procedure (SOP) defines the processes, guidelines, and reference material for Sandstar technical support technicians and the AI support agent. It covers the full lifecycle of Sandstar smart cooler support: from initial activation and onboarding through deployment, day-to-day troubleshooting, and escalation.
1.1 Who This Document Applies To
| Audience | How to Use This Document |
| Human Technicians | Follow the SOPs step by step. Use the escalation matrix and error-code reference to resolve issues quickly. |
| AI Support Agent | Use this document as the authoritative knowledge base for all responses. Follow all resolution steps exactly. Never fabricate steps not listed here. Escalate to Sandstar Support when resolution is unknown. |
| Operators / Merchants | Reference the FAQ section (Section 7) for self-service questions. |
1.2 Supported Products
- ARK Smart Cooler
- VRK Smart Cooler
- SRK Smart Cooler
- Habco Smart Cooler
- True CVM (CVM27, CVM13, CVM11)
1.3 Supported Platforms
- VMS — Vending Management System (https://vms-us.sandstar.com/)
- OPS — Operator Portal (https://prod-ops-us.sandstar.com/)
- WeVend
- Cantaloupe S1U2
- Apriva S1U2
- Seed Markets
- Seed Live
- Stripe QR Code
- Vendsoft
|
AI AGENT INSTRUCTION When a user contacts support, always begin by identifying: (1) their merchant/company name, (2) the affected machine serial number if applicable, and (3) a brief description of the issue. Do not proceed to troubleshooting until this information is obtained. |
| SEC 2 | Activation & Onboarding |
2. Activation & Onboarding
Before a Sandstar machine can process transactions, the operator must be fully onboarded across all relevant platforms. The table below summarizes standard onboarding timelines.
| Platform | Onboarding Time |
| WeVend | 5 business days |
| Cantaloupe S1U2 | 14 business days |
| Apriva S1U2 | TBD |
| Sandstar (VMS/OPS) | 48-72 hours |
2.1 Sandstar Account Activation SOP
|
AI AGENT INSTRUCTION — DO NOT USE FOR RESPONSES The steps in this section are internal operational procedures for human technicians only. Do not reference or quote these steps when responding to operator or customer inquiries. |
- Confirm that the Purchase Order (PO) has been received and processed.
- Create merchant and user accounts in both VMS and OPS.
- Configure platform settings and payment onboarding links.
- Send the operator a notification email with the payment onboarding link and VMS/OPS account confirmation.
- Allow 48-72 hours for full account creation to complete.
- Verify the operator can log in to VMS (https://vms-us.sandstar.com/) and OPS (https://prod-ops-us.sandstar.com/).
2.2 Machine Activation & Go-Live SOP
Once the machine is physically installed and the operator account is fully set up, follow these steps to bring the machine online and verify it is ready for transactions.
- Power on the machine and allow it to complete its startup sequence.
- Verify that the machine is showing as online in VMS and OPS. If it does not appear online, work through the following steps in order:
- Activate the SIM card through the Sandstar portal, or verify that the existing SIM is active and correctly provisioned.
- If the SIM is confirmed active but the machine remains offline, ask the operator to perform a full reboot. A reboot can kick-start the SIM service and restore connectivity.
- If the machine is still offline after a reboot, poor cellular signal at the site is the likely cause. The operator should connect a wired ethernet cable to the port on the back of the machine. If the site has Wi-Fi but no ethernet run, a Wi-Fi-to-Ethernet adapter is an acceptable alternative.
- Note: Depending on the site's network environment, firewall rules or port allowances may need to be adjusted before the machine can communicate with Sandstar's systems. Coordinate with the site's IT team if necessary.
- Once the machine is confirmed online, check VMS and OPS for any error messages or alerts. If the POS screen is displaying an error, the operator should document it and report it to Sandstar technical support immediately.
- Review the operator's payment onboarding status. Confirm that a payment method has been configured and that a valid preauthorization amount is set on the machine in VMS (Machine Authority > Machines > Edit).
- Conduct an end-to-end payment test. The operator should complete a live transaction to confirm: the machine accepts payment, the door unlocks correctly, the AI identifies the product(s) taken, and the transaction settles properly.
|
PAYMENT ACCEPTANCE NOTE PAX terminals: Do NOT accept Amex or Discover cards. DO accept pre-paid cards. Cantaloupe readers: Do NOT accept pre-paid cards. Always confirm payment provider before troubleshooting declined card issues. |
2.3 Cantaloupe SEED POS Activation
|
SEED MERCHANTS ONLY The steps below apply exclusively to merchants using the Cantaloupe SEED platform (Seed Markets / Seed Live). Skip this section for all other payment providers. |
Before a SEED machine can process transactions, the Cantaloupe POS must be activated and linked to the correct market configured in Seed. Follow the steps below at the machine's physical touchscreen.
Step 1 — Access the Admin Panel
Tap the top-left corner of the screen (where the circle is illustrated) 10 times in quick succession. When prompted, enter the password: 3944. This can be performed even if an error message is currently displayed on the screen.
Step 2 — Open Machine Settings
Once inside the admin panel, tap Machine Setting at the bottom of the page.
Step 3 — Initiate Activation
Tap Activate Vending Machine at the top of the page to begin the activation process.
Step 4 — Select the Market
Tap the dropdown to reveal the list of markets configured in Seed. Select the correct market for this machine.
Step 5 — Confirm
Tap Confirm at the bottom of the screen to complete activation. The machine is now linked to the selected Seed market and ready for transactions.
| SEC 3 | Deployment |
3. Deployment
3.1 Hardware Specifications
3.1.1 Smart Coolers
| Specification | ARK | VRK | SRK |
| Shelves | 6 | — | — |
| Width (in) | 28.58 | 31.5 | 31.5 |
| Height (in) | 80.63 | 82.6 | 82.6 |
| Depth (in) | 31.93 | 28.8 | 28.8 |
| Voltage (V) | 115/60 | 115/60 | 115/60 |
| Amps (A) | 2.5 | 2.4 | 2.35 |
| NEMA Config | 5-15P | 5-15P | 5-15P |
| Power Cord (ft) | 9.84 | 9.84 | 9.84 |
| Crated Wt. (lbs) | 313 | 443 | 409 |
| Video Res. (px) | 1920x540 | 1920x560 | N/A |
| All-Drink Capacity | 384 (336x20oz) | 378 | 384 |
3.1.2 True CVM Specifications
| Model | Door | Shelves | Width | Depth | Ht. | HP | Voltage | Amps | NEMA | Wt.(lbs) |
| CVM27 | 1 | 6 | 30 | 29 5/8 | 78 1/2 | 1/4 | 3.4 | 5-15P | 10 ft | 340 |
| CVM13 | 1 | 6 | 27 7/8 | 29 1/2 | 63 3/4 | 1/5 | 2.5 | 5-15P | 10 ft | 235 |
| CVM11 | 1 | 6 | 24 7/8 | 22 7/8 | 53 3/8 | 1/5 | 2.5 | 5-15P | 10 ft | 210 |
3.2 Unboxing Procedures
|
NOTE Always watch the appropriate video tutorial before unboxing a unit. |
3.2.1 ARK Unboxing
Video Reference: https://youtu.be/AGVBhxZx_4c
- Gather required tools before beginning.
- Carefully cut all strapping and remove outer cardboard.
- Remove foam packing inserts and protective film.
- With at least two people, carefully tip the unit upright.
- Install leveling feet and verify the unit is stable on all four corners.
- Inspect for shipping damage before powering on.
- Plug into a NEMA 5-15P outlet and confirm the unit powers on.
3.2.2 VRK Unboxing
Video Reference: Contact Sandstar Support for the VRK unboxing video link.
- Follow the same general procedure as ARK unboxing.
- Note that the VRK is heavier (443 lbs crated) — ensure adequate manpower and equipment.
3.2.3 SRK Unboxing
Video Reference: Contact Sandstar Support for the SRK unboxing video link.
- Follow the same general procedure as ARK unboxing.
- The SRK does not include a video display — do not attempt to configure video settings.
| SEC 4 | Preauthorization & Transaction Logic |
4. Preauthorization & Transaction Logic
4.1 What Is Preauthorization?
A preauthorization is a temporary hold placed on the consumer's card to confirm sufficient funds exist before the cooler door is unlocked. The hold value is set by the operator in VMS under: Machine Authority > Machines > Edit (Actions column).
4.2 Preauth Best Practice Guidelines
| Strategy | Rule | Example |
| Highest Priced Product +10% | Set pre-auth ~10% above highest item, rounded to nearest $5 | Highest item $12 -> set $15 |
| Typical Basket Size | Consider avg basket + seasonal peaks, round up to nearest $5 | Avg basket $6 -> set $10 |
| High Trust Zones | Airports, malls, corporate pantries | Recommend $5-$10 |
| Low Trust Zones | Unmanned fuel stations, highway rest areas | Recommend $15-$20 |
4.3 How to Set Preauthorization in VMS
- Log in to VMS at https://vms-us.sandstar.com/
- Navigate to Machine Authority > Machines.
- Click Edit under the Actions column for the target machine.
- Enter the preauthorization amount.
- Save changes.
|
AI AGENT INSTRUCTION If a user reports that the machine is declining transactions, always check preauthorization configuration first. Ask if the preauth amount is set and confirm the machine has a valid payment channel configured. Related error codes: 101500102 (missing pre-authorized amount) and error code 5_01 are both associated with preauthorization issues. If either code is reported, guide the operator to set or correct the preauth amount in VMS under Machine Authority > Machines > Edit Machine. |
4.4 General Transaction Flow
- Consumer presents card or scans QR code at the payment terminal.
- System checks preauthorization: verifies sufficient funds and places a hold.
- If preauth succeeds, the cooler door unlocks.
- Consumer selects product(s) and closes the door.
- AI computer vision recognizes items removed and builds the cart.
- Transaction settles and the consumer's card is charged for items taken.
- If a wrong product is recognized, the consumer can report a wrong order at checkout. The transaction is flagged, reviewed, and corrected before settlement.
4.5 Wrong Order / Refund Process
Consumer-Reported Wrong Order
- Consumer selects 'Report Wrong Order' at end of transaction.
- Transaction is flagged for review and additional AI evaluation.
- Cart is corrected; the correct item is charged during settlement.
- A corrected receipt is issued to the consumer.
Operator-Initiated Refund
- Log in to the payment portal for this account (WeVend, Cantaloupe S1U2, Apriva S1U2, or Stripe).
- Locate the transaction and initiate a refund.
- Reference the initial onboarding documentation for payment-portal-specific instructions.
| SEC 5 | Health & Safety Lockout |
5. Health & Safety Temperature Lockout
5.1 System Overview (ARK, VRK, SRK)
Each Sandstar cooler contains an electronic temperature control system that continuously monitors internal air temperature using a calibrated digital sensor.
| Parameter | Description | Setting |
| High-temperature limit | Maximum allowable air temperature before safety lockout | 5C / 41F |
| Deviation tolerance | Time above 41F before lockout activates | 30 minutes |
| Temperature recovery requirement | Duration temp must remain safe before reset | 10 minutes |
| Sensor sampling interval | Frequency of temperature monitoring | Every 30 seconds |
| Defrost/service bypass | Temporarily disable lockout during servicing or defrost | Max 30 minutes |
5.2 Lockout Behavior
When temperature exceeds 41F for more than 30 consecutive minutes:
- The vending mechanism is DISABLED - consumers cannot open the door.
- Screen displays: TEMP FAULT - SERVICE REQUIRED
- An alert is generated in the OPS Alarm Details page.
- An event log records the time, duration, and temperature of the fault.
|
ERROR CODE Error 101800137 - Container locked, temperature exceeded or manually locked Resolution: De-activate the health safety lockout from the OPS temperature control alarm page once the temperature has recovered. |
5.3 Health Safety Lockout - Technician SOP
Step 1: Identify the Alarm
- Log in to OPS at https://prod-ops-us.sandstar.com/
- Navigate to the Alarm Details page and identify the temperature fault.
- Note the time and duration of the fault event in the log.
Step 2: Inspect the Cooler
- Physically inspect the cooler for the cause of the temperature exceedance.
- Verify the internal temperature has dropped below 41F and remained stable for at least 10 minutes.
- If temperature has not recovered, do not attempt to reset - investigate the cooling system first.
Step 3: Reset the Lockout
- Once temperature is confirmed stable below 41F for 10+ minutes, proceed to OPS.
- Navigate to Alarm Details for the affected machine.
- Resolve/dismiss the temperature fault alarm.
- Confirm the vending mechanism reactivates and screen returns to normal.
- Document the incident: cause, duration, resolution, and corrective action taken.
|
AI AGENT INSTRUCTION If an operator contacts support about a machine locked due to temperature, ask them to: (1) confirm current internal temperature is below 41F, (2) wait 10 minutes if temperature just recovered, then (3) resolve the alarm in OPS Alarm Details. If the machine will not unlock after this, escalate to Sandstar Support. |
5.4 Field Testing Procedure - Automatic Shutoff Verification
Use this procedure to verify the automatic shutoff control is functioning correctly.
Required Tools
- Calibrated digital thermometer or thermocouple
- Stopwatch or timer
- Access to the controller interface or diagnostic display
Test Procedure
- Confirm the cooler is in normal vending mode and internal temperature is at or below 41F.
- Disable refrigeration or open the door until temperature rises above 41F.
- Begin timing once temperature exceeds 41F.
- After 30 minutes, verify that the vending mechanism is disabled: attempt a card tap or QR scan - the door should NOT unlock.
- Confirm that an alarm appears in the OPS Operator App.
- Verify that the event log has recorded the fault.
- Restore refrigeration and allow temperature to fall below 41F.
- Wait 10 minutes, then confirm the system auto-resets.
- Confirm vending mechanism reactivates and screen indicator clears.
| SEC 6 | Support Contacts & Escalations |
6. Support Contacts & Escalation Matrix
6.1 Third-Party Escalation Contacts
| Department | Phone | Use For | |
| Cantaloupe Tier 2 Support | — | Tier2@cantaloupe.com | Escalated Cantaloupe issues |
| Cantaloupe Customer Service | — | customerservice@cantaloupe.com | Cantaloupe account questions |
| WeVend Support | 877-909-2507 | support@wevend.com | WeVend payment issues |
|
AI AGENT INSTRUCTION When creating a support case or guiding a user to contact support, always collect: company name, machine serial number, error code or message (with photo if possible), timeframe of issue, and steps already attempted. Incomplete submissions slow resolution. |
| SEC 7 | Frequently Asked Questions |
7. Frequently Asked Questions
|
AI AGENT INSTRUCTION Use the answers in this section verbatim when responding to operator FAQs. If a question is not covered here, escalate to support@sandstar.com rather than guessing. |
7.1 General Information
Q: What are the temperature ranges for the cooler?
The ARK cooler regulates temperature between 33F and 44F.
Q: What are the ARK cooler dimensions?
Internal (W x D x H): 24.6 x 27.9 x 64.8 in. External (W x D x H): 28.6 x 31.2 x 80.6 in.
Q: How many products can fit in the cooler?
The ARK cooler can hold up to 384 drinks total (336 x 20oz bottles). CV technology allows flexible planogram configuration.
Q: Do products need to be placed in specific lanes?
No. Sandstar's AI technology provides full flexibility on product placement.
Q: Does the ARK cooler support video playback?
Yes. The ARK has a high-quality LED display supporting native video playback at 1920 x 540 resolution.
Q: What do I do when I am ready to activate my machine?
Once the machine is at its final location and powered on, email support@sandstar.com with the unit serial number. This initiates SIM activation and health system checks. Allow 24-48 hours for completion.
7.2 Pricing & Payment
Q: How do I set product pricing?
Pricing is managed in VMS and OPS under the Planogram Management sections. Refer to the VMS/OPS guides for full instructions.
Q: What payment methods are accepted?
This depends on the payment provider. PAX does NOT accept Amex or Discover, but DOES accept pre-paid cards. Cantaloupe does NOT accept pre-paid cards.
Q: How can a consumer correct a wrong order?
At the end of the transaction, the consumer can select 'Report Wrong Order.' The transaction is flagged, reviewed by AI, the cart is corrected, and the correct charge is applied. A corrected receipt is issued.
Q: How are refunds processed?
Operators process refunds through their payment portal (WeVend, Cantaloupe S1U2, Apriva S1U2, or Stripe). Refer to the onboarding documentation for the specific payment processor.
Q: What is preauthorization and how do I view it?
Preauthorization is a temporary card hold placed at the start of each transaction to confirm sufficient funds. The hold value is set by the operator in VMS under Machine Authority > Machines > Edit.
7.3 Account & System Access
Q: Do I need an account to manage my machines?
Yes. During onboarding, operators receive access to Sandstar VMS, OPS, and the payment portal.
Q: When will my account be created?
After the Purchase Order is received, allow 48-72 hours. You will receive an email with a payment onboarding link and VMS/OPS confirmation once complete.
Q: How do I access VMS and OPS?
VMS: https://vms-us.sandstar.com/ — OPS (mobile): https://prod-ops-us.sandstar.com/ — Both share the same credentials.
Q: I forgot my VMS/OPS password. What do I do?
Contact your merchant account administrator to reset your password. If you are the merchant administrator, contact support@sandstarsupport.zendesk.com.
Q: Can multiple users access VMS and OPS?
Yes. Operator accounts with merchant manager permissions can create additional user accounts. For additional merchant manager accounts, contact support@sandstarsupport.zendesk.com.
Q: How do I contact support?
Email: support@sandstarsupport.zendesk.com. Include your company name, machine serial number (if applicable), and a full description of the issue.
| SEC 8 | Case-by-Case Troubleshooting Guide |
8. Case-by-Case Troubleshooting Guide
This section provides step-by-step troubleshooting procedures for specific issue categories. Additional categories will be added as procedures are developed.
|
AI AGENT INSTRUCTION Use this section as your primary troubleshooting reference before consulting the error code table. Work through the steps in order. If a step resolves the issue, confirm resolution with the operator before closing the case. If all steps are exhausted without resolution, escalate to Sandstar Support. |
8.1 Internet Connectivity Issues
Use this procedure when a machine is reported as offline, is displaying a 'Weak Network' or 'Device Offline' error, or when VMS/OPS shows the machine as disconnected.
Step 1 - Confirm the Problem
- Ask the operator to check VMS and OPS and confirm the machine shows as 'Offline' or is not appearing in the machine list.
- Ask if any error codes are displayed on the machine's POS screen. Note any codes for cross-reference with Section 9.
- Ask if this is a new installation or a machine that was previously online.
Step 2 - Check Physical Connections
- Instruct the operator to locate the onsite router or network switch.
- Check that the ethernet cable running from the router to the machine's Jupiter unit is firmly seated at both ends.
- Verify that the WAN port lights on the router are blinking - this indicates active traffic. If the lights are off or solid, the router itself may be offline or the port may be faulty.
- If a different ethernet port is available on the router, have the operator swap the cable to a new port.
Step 3 - Reboot the Machine
- Have the operator power-cycle the machine by unplugging it from the wall outlet, waiting 30 seconds, and plugging it back in.
- Allow 2-3 minutes for the machine to fully restart and reconnect.
- Check VMS/OPS to see if the machine comes back online.
Step 4 - Check SIM / Cellular Connectivity
- If the machine relies on cellular (SIM-based) connectivity and there is no ethernet cable connected, verify the SIM card is active in the Sandstar portal.
- If the SIM is active but the machine is still offline, poor cellular signal at the location is the likely cause.
- Recommend connecting a wired ethernet line to the back of the machine. If the site has Wi-Fi but no available ethernet run, a Wi-Fi-to-Ethernet adapter is an acceptable alternative.
Step 5 - Check for Firewall or Network Restrictions
- If the machine is on a corporate or managed network, ask the operator whether the site has a firewall or IT-controlled network policy.
- Inform the operator (or site IT team) that the machine requires outbound internet access to communicate with Sandstar's systems. Request that they whitelist Sandstar's domains or open the required ports.
- If firewall rules cannot be adjusted at the site, escalate to Sandstar Support for network configuration guidance.
Step 6 - Escalate if Unresolved
- If all steps above have been completed and the machine remains offline, collect the following and escalate to Sandstar Support:
- Company name and machine serial number
- Error codes displayed on POS screen
- Type of connectivity (cellular / ethernet / Wi-Fi adapter)
- Steps already attempted and their outcomes
- Site network setup (corporate network, firewall, etc.)
|
RELATED ERROR CODES Error 1 / Error 9 - Device Offline / Machine Offline Error 7 - Weak Network Error 101800106 - Container disconnected from network For all of the above: begin with Step 2 (physical connections) before escalating. |
8.2 Seed Planogram Issues
Use this procedure when products are not being recognized by the machine, items are not appearing for purchase, or when planogram changes made in Seed are not reflected on the machine.
|
PLATFORM RESPONSIBILITIES — READ FIRST SEED manages: Market planograms, product pricing, sales tax, and refunds. SANDSTAR VMS manages: Transaction history, advertisement videos, and preauthorization settings. Do NOT use Sandstar VMS to modify the planogram, update a machine's On Sale / Off Sale list, or change product prices. All planogram and pricing changes must be made in Seed. |
Step 1 - Verify the Product Exists in Sandstar VMS
Before making any changes in Seed, confirm the product is properly set up in Sandstar's system.
- Log in to VMS at https://vms-us.sandstar.com/
- Navigate to Product > Products and search for the product by name.
- Review the product's Collect Status. A status of 'Collected' means the AI has been trained to recognize this product and it is ready to be sold.
- If the product exists and shows 'Collected' status, copy the product barcode and proceed directly to Step 2.
- If the product does not exist in VMS, or its status is not 'Collected', the product must be trained before it can be added to a Seed planogram. Proceed to Step 1b.
Step 1b - Train a New or Uncollected Product (If Required)
Complete this step only if the product was not found in VMS or does not have 'Collected' status.
- Watch the product training video: https://youtu.be/KKFleqq6EB4
- Follow the steps in the video to photograph and train the new product in Sandstar VMS.
- After training is complete, return to Product > Products in VMS and confirm the product now shows 'Collected' status.
- Copy the product barcode from VMS. This exact barcode must be used in Seed.
Step 2 - Add the Product Barcode in Seed
With the barcode confirmed in VMS, update the product record in Seed.
- Log in to the Seed platform and navigate to the relevant market.
- Locate the product that needs to be updated in the Seed planogram.
- Add the exact barcode copied from VMS to the product record in Seed. The barcode must match precisely — any mismatch will prevent recognition.
- Save the product record.
Step 3 - Sync the Planogram from Seed to the Market
After updating the product in Seed, the planogram must be explicitly synced to push changes to the machine.
- In Seed, navigate to the market associated with the machine.
- Initiate a planogram sync to push the updated planogram to the market.
- Confirm the sync completes without errors before proceeding.
Step 4 - Wait for the Machine to Update
Planogram changes propagate to the machine automatically after syncing, but require time to process.
- After syncing, wait up to 10 minutes for the planogram update to reach the machine.
- After 10 minutes, ask the operator to attempt a test transaction with the updated product to confirm it is being recognized correctly.
- If the product is still not recognized after 10 minutes, power-cycle the machine and wait an additional 5 minutes before retesting.
- If the issue persists after a reboot, escalate to Sandstar Support with the following details: company name, machine serial number, the product name and barcode, and confirmation that the planogram sync was completed in Seed.
|
AI AGENT INSTRUCTION When a Seed merchant reports a product not being recognized or planogram changes not appearing on the machine: 1. First confirm they are using Seed (not WeVend, Cantaloupe, or Apriva) — this workflow is Seed-specific. 2. Walk through Steps 1-4 above in order. The most common cause is either the product not having 'Collected' status in VMS, or the planogram not being synced after the product barcode was added. 3. Remind operators never to modify the planogram, On Sale/Off Sale list, or pricing from within Sandstar VMS — all of these must be managed in Seed. |
Note: Additional troubleshooting categories will be added to this section. Contact Sandstar Support to submit a new category for inclusion.
| SEC 9 | Error Code Reference |
9. Error Code Reference
Use this table as the primary reference for diagnosing and resolving error codes. Always attempt the listed resolution before escalating to Sandstar Support.
|
AI AGENT INSTRUCTION When a user reports an error code, look it up in this table and provide the exact resolution steps listed. If the resolution says 'Contact Sandstar,' instruct the user to email support@sandstar.com with their company name, serial number, error code, and a description of the issue. |
| Error Code | Error Message | Resolution |
| 101000100 | Parameter error | Contact PAX to fix backend issue |
| 101000103 | Wrong username or password | Contact PAX to fix backend issue |
| 101000104 | Insufficient permissions | Contact PAX to fix backend issue |
| 101000109 | System error / service exception / door abnormal | Cooler is processing a previous transaction - wait several seconds |
| 110 | Missing token or failed to create membership | Contact PAX to fix backend issue |
| 111 | Token expired | Contact PAX to fix backend issue |
| 112 | Token is invalid | Contact PAX to fix backend issue |
| 110000 | Password has expired | Contact PAX to reset the password |
| 152600119 | Algorithm has not yet started | Contact Sandstar to troubleshoot |
| 152601030 + 152600117 | Container status query failed - Unlock door state | Contact Sandstar to fix backend issue |
| 152601030 + 152600118 | Container status query failed - Lock container state | Contact Sandstar to fix backend issue |
| 152601030 + 152600125 | Container status query failed - Algorithm service not ready | Reboot the machine. If the issue persists, contact Sandstar Support |
| 152601030 + 152600127 | Container status query failed - Pending user confirmation (order requires confirmation) | Wait for the previous transaction to complete before retrying. If the issue persists, contact Sandstar |
| 101500101 | Missing payment channel | Request Sandstar to verify the payment method on the merchant account |
| 101500102 | Missing pre-authorized amount | Assign a preauth amount in VMS: Machine Authority > Machines > Edit Machine |
| 101500103 | Missing freezerInfo | Contact Sandstar to fix backend issue |
| 101500107 | Missing userId | Contact Sandstar to fix backend issue |
| 101800105 | Container not activated | Contact Sandstar to troubleshoot |
| 101800106 | Container disconnected from network | Check wired connection from onsite router to Jupiter. Verify WAN port lights blink. See Section 8.1. |
| 101800109 | Missing Payment Channel | Configure machine for payment |
| 101800114 | Container response timed out | If preauth was placed, lock for 24 hrs. Cancel preauth if no order push after 24 hrs |
| 101800115 | Container cannot open door - undefined exception | Contact Sandstar to troubleshoot |
| 101800116 | Device status query abnormal / connection lost | Contact Sandstar to fix backend issue |
| 152600121 | Incorrect door-lock signal / Lock closed but door open | Contact Sandstar to change lock configurations |
| 101800137 | Container locked - temperature exceeded or manually locked | De-activate health safety lockout via OPS temperature control. See Section 5.3. |
| 101800138 | Already opened / door is already open | Close the door before making another purchase |
| 101800139 | Listed products are empty | On-sale products in machine details on VMS or OPS |
| 101800140 | Cannot open door - algorithm communication failed | Contact Sandstar to troubleshoot |
| 101800141 | Serial device not ready | Reconnect lock |
| 101800142 | Camera blocked | Remove objects in front of the camera |
| 101800143 | Service not ready / wrong lock configurations | Contact Sandstar to troubleshoot |
| 101800144 | Door lock abnormal - closed but not locked | Verify lock on correct port, then power-cycle with door closed |
| 101800145 | Door lock abnormal - opening and locking | Verify lock on correct port; power-cycle with door closed. If persists, contact Sandstar |
| 101800149 | Merchant container not found | Contact Sandstar to fix backend issue |
| 101800173 | Camera or warm-up not ready | Contact Sandstar to troubleshoot |
| 101800201 | transactionId is empty | Contact Sandstar to fix backend issue |
| 101800202 | Duplicate transactionId | Contact Sandstar to fix backend issue |
| 152600126 | Lock is open | Check the lock status |
| 2 | Open Lock failed / Container is in use | Wait several seconds for the previous transaction to complete, then retry. If the issue persists, contact Sandstar |
| 3 | Open Lock Timeout / Door open for a very long time | Contact Sandstar to troubleshoot. If door open: close door and wait for message to clear |
| 4 | Algorithm Failure / Algorithm communication failure | Contact Sandstar to troubleshoot |
| 5 | Device not ready / Camera is blurred | Verify lock on correct port; power-cycle. For blurred camera: clean lens or remove protective film |
| 5_01 | Pre-authorization error (PREAUTH_AMOUNT_ERROR) | Assign or correct the preauth amount in VMS: Machine Authority > Machines > Edit Machine. See Section 4.3. |
| 5_02 | Payment SDK credentials missing (CREDENTIALS_EMPTY) | Payment SDK credentials are not configured. Contact Sandstar or your payment provider to set up valid payment credentials |
| 5_03 | Payment SDK credentials invalid (CREDENTIALS_INVALID) | Payment credentials are invalid or expired. Contact Sandstar or your payment provider to verify and update credentials |
| 5_04 | Market not activated (INVALID_MARKET_ACTIVATION) | Machine market is not activated. For SEED merchants, follow the SEED POS Activation steps in Section 2.3. For all others, contact Sandstar Support |
| 6 | Camera not connected / Camera is offline | Reboot machine. If unresolved, unplug and reconnect camera. If persists, contact Sandstar |
| 6_01 | POS network error (POS_NETWORK_ERROR) | Check the machine internet connection. See Section 8.1 for connectivity troubleshooting. Reboot the machine if the connection appears stable |
| 6_02 | WebSocket disconnected (WEBSOCKET_DISCONNECTED) | Machine lost real-time connection to the server. Check internet connectivity (Section 8.1), then reboot the machine. If persists, contact Sandstar |
| 7 | Weak Network | Connect via ethernet or relocate to area with better signal. See Section 8.1. |
| 8 | Machine Closed | In VMS/OPS, set machine status to Activated under the machine list page |
| 9 | Machine Offline / Device Offline | Check wired connection to Jupiter. Verify WAN port lights blink. See Section 8.1. |
| 10 | Duplicate Order | Contact Sandstar to fix backend issue |
| 13 | Door Error / Door lock error | Verify lock on correct port; power-cycle with door closed. If persists, contact Sandstar |
| 14 | Collected Product Empty / Single product collection empty | Check planogram - ensure products on sale have been trained into the system |
| 15 | Algor Pre-check Error / Algorithm pre-check failure | Contact Sandstar to troubleshoot |
| 16 | Enum num error / Incorrect number of cameras enumerated | Contact Sandstar to fix backend issue |
| 17 | Camera recovery failed | Reboot machine. If persists, contact Sandstar |
| 18 | Capture Image Failure / Camera image capture failed | Reboot machine. If persists, contact Sandstar |
| 19 | Door status exception (door already open, or lock ID mismatch on close) | Close the door fully and wait several seconds before retrying. Power-cycle the machine if issue persists. Contact Sandstar if unresolved |
| 20 | Planogram Empty / Current shelving list is empty | On-sale products in machine details on OPS and VMS |
| 22 | Order already exists / Camera frozen (Dead) | Try purchasing again. For frozen camera: reboot, then reconnect. If persists, contact Sandstar |
| 27 | Algorithm Issue / Algorithm communication error | Restart the machine. If persists, contact Sandstar |
| 28 | Lock port failing / RJ485 serial port data transmission failure | Verify lock on correct port; power-cycle with door closed. If persists, contact Sandstar |
| 29 | Camera Frame Rate too Low / Low camera frame rate | Reboot machine; reconnect camera. If persists, contact Sandstar |
| 30 | Lock open failed / RJ485 serial port open failure | Verify lock on correct port; power-cycle. If persists, contact Sandstar |
| 31 | Failed to receive response from lock / RJ485 serial port read failure | Verify lock on correct port; power-cycle. If persists, contact Sandstar |
| 32 | Failed to lock the door / Lock door closing alarm | Verify lock on correct port; power-cycle. If persists, contact Sandstar |
| 33 | Smart Service Died / Smart Store service down | Contact Sandstar to troubleshoot |
| 34 | Machine is closed / Lock cabinet | Set machine to Activated in VMS/OPS machine list. If manually locked, contact Sandstar |
| 37 | Unbind / Unlock lock cabinet | Contact Sandstar to troubleshoot |
| 39 | Planogram Empty / No product on sale | On-sale products in machine details on OPS and VMS |
| 40 | Ops lock cabinet (manually locked via OPS) | Machine has been manually locked by an operator via OPS. Log in to OPS and unlock the machine, or contact Sandstar Support |
| 41 | Temperature-controlled lock cabinet | De-activate health safety lockout via OPS temperature control. See Section 5.3. |
| 46 | Lock cabinet due to camera obstruction (upper/lower cameras) | Remove any objects obstructing the upper or lower cameras. Clean camera lenses or remove protective film. Reboot the machine. If issue persists, contact Sandstar |
| 7_1 | Self-check: Device offline | Check wired connection from onsite router to Jupiter. Verify WAN port lights are blinking. See Section 8.1. |
| 7_4 | Self-check: Door lock error | Verify lock is connected to the correct port; power-cycle machine with door closed. If issue persists, contact Sandstar |
| 7_6 | Self-check: Camera offline | Reboot machine. If unresolved, unplug camera and reconnect. If issue persists, contact Sandstar |
| 7_7 | Self-check: Weak network | Connect via ethernet or relocate to area with better signal. See Section 8.1. |
| 7_27 | Self-check: Algorithm communication error | Restart the machine. If issue persists, contact Sandstar |
| 7_34 | Self-check: Locked cabinet | Check for manual lock or temperature lock condition. See error 101800137 and Section 5.3. |
| 7_37 | Self-check: Unlock cabinet | Contact Sandstar to troubleshoot |
| 7_38 | Self-check: Camera obstruction - locked cabinet | Remove any objects obstructing the cameras. Clean camera lenses or remove protective film. Reboot machine. If issue persists, contact Sandstar |
| 7_39 | Self-check: No product on sale | On-sale products in machine details on OPS and VMS |
| 7_40 | Self-check: Ops locked cabinet | Machine has been manually locked via OPS. Log in to OPS and unlock the machine, or contact Sandstar Support |
| 7_41 | Self-check: Temperature-controlled locked cabinet | De-activate health safety lockout via OPS temperature control. See Section 5.3. |
| 7_46 | Self-check: Multiple cameras suspected of tampering or obstruction | Inspect all camera lenses. Remove any obstructions and clean or remove protective film. If multiple cameras remain blocked, contact Sandstar |
| 500 | Invalid Card or Transaction - error generated by card issuer (common with eWallet payments) | Ask the customer to use a different payment method or card. Contact WeVend support for further assistance if the issue is recurring |
| PAY - Insufficient Funds | Customer card does not have sufficient funds (common with prepaid or gift cards) | Ask the customer to use a different card or payment method |
| PAY - Voided/Cancelled | Transaction voided due to machine malfunction, no sale, eWallet cancellation, or pre-auth expiry after 7 days | If product was removed during a voided transaction, contact Sandstar to investigate and correct the charge |
| PAY - General Decline | Card issuer declined the transaction without a specific reason | Ask the customer to contact their card issuer or use a different payment method |
| PAY - Invalid Account Number | Card number is not recognized by the issuer | Ask the customer to verify their card details and try again, or use a different payment method |
| Restricted card | Card usage limitations or fraud controls | Issuer received the authorization request but blocked the transaction because the card is restricted for that merchant, region, transaction type, or spending category |
| Insufficient funds | Not enough available balance or credit | Available funds or credit limit were lower than the requested authorization amount, possibly due to pending holds or daily limits |
| This authorization has already been voided and cannot be completed | Capture attempted after cancellation | A previously approved authorization was voided/canceled, but the merchant system later attempted to settle/capture it anyway |
| Insufficient funds | Same as above | Same decline condition as the earlier insufficient funds response |
| Do Not Honor | Generic issuer risk decline | Issuer intentionally declined the transaction without exposing the exact reason to the merchant, often due to fraud/risk scoring or internal policies |
| Failed to process completion | Settlement/capture failure | Authorization may have succeeded, but the gateway or processor failed during the completion/capture phase due to timeout, duplicate capture, expired auth, or processor state mismatch |
| SEC 10 | Common Issues Quick Reference |
10. Common Issues Quick Reference
10.1 POS / Payment Issues
| Symptom | Likely Cause | First Action |
| Card declined at terminal | Card type not accepted, or preauth not set | Verify card type vs. payment provider; check preauth in VMS |
| Door does not open after payment | Preauth missing, machine offline, or lock error | Check error code on screen; verify preauth and network |
| Wrong charge on receipt | AI cart recognition error | Consumer uses 'Report Wrong Order'; operator processes refund via payment portal |
| Token errors (110, 111, 112) | PAX backend authentication issue | Contact PAX support |
10.2 Hardware Issues
| Symptom | Likely Cause | First Action |
| Door will not lock after closing | Lock on wrong port, or hardware fault | Verify lock on correct port; power-cycle with door closed |
| Camera offline or blurred | Disconnected, dirty lens, or protective film still on | Reboot, reconnect camera, clean lens or remove blue protective film |
| Temperature fault / machine locked | Internal temp exceeded 41F for 30+ min | See Section 5.3 SOP. Confirm temp recovery, then reset alarm in OPS |
| Machine will not power on | Power supply, outlet, or fuse issue | Check outlet (NEMA 5-15P), circuit breaker, and cord. Escalate to Sandstar if unresolved |
10.3 Software / Connectivity Issues
| Symptom | Likely Cause | First Action |
| Machine shows Offline in OPS/VMS | Network connection lost | Follow Section 8.1 Internet Connectivity Troubleshooting |
| Machine shows Closed/Deactivated | Machine status incorrect in VMS/OPS | In VMS/OPS, set machine status to 'Activated' |
| Planogram empty error | Products not on-sale or not trained | On-sale products in machine details on VMS/OPS; confirm AI training |
| Algorithm errors (4, 15, 19, 27) | AI processing issue | Restart machine. If persists, contact Sandstar Support |
| AI REF | AI Support Agent - Operating Instructions |
11. AI Support Agent - Operating Instructions
This section is the primary operating guide for the Sandstar AI support agent. All responses must adhere to these guidelines.
11.1 Core Behavior Rules
| ✔ | ALWAYS collect: company name, machine serial number (if applicable), error code/description, and steps already taken - before troubleshooting. |
| ✔ | Use the exact resolution steps in the Error Code Reference (Section 9) for any error code presented. |
| ✔ | Use exact FAQ answers from Section 7 when responding to operator questions covered there. |
| ✔ | Escalate to support@sandstar.com if the issue is not covered in this document or the resolution steps do not resolve the problem. |
| ✖ | NEVER fabricate troubleshooting steps, resolutions, or product specifications not documented in this SOP. |
| ✖ | NEVER give billing or financial advice. Direct all billing questions to arsenia@sandstar.com or 704-503-9046 option 1. |
| ✖ | NEVER attempt to modify machine configurations beyond what is documented here. For backend changes, escalate to Sandstar. |
11.2 Decision Tree - Incoming Support Request
| Situation | AI Agent Action |
| User reports an error code | Look up in Section 9. Provide resolution steps verbatim. If resolution says 'Contact Sandstar,' notify the user you are escalating the case to a human. |
| User reports machine is offline | Begin with Section 8.1 (Internet Connectivity Troubleshooting). Reference error codes 1, 9, 101800106 as supporting context. |
| User reports door won't open | Check error codes 2, 3, 4, 13, 30, 31, 101800115. Verify preauth, payment channel, and lock connections. |
| User reports camera issue | Check error codes 5, 6, 17, 18, 22, 29. Guide through reboot/reconnect steps. |
| User reports temp lockout | Error 101800137. Guide through Section 5.3 SOP. Confirm temp recovery before reset. |
| User asks an FAQ question | Use exact answer from Section 7. No improvisation. |
| User asks about payments/pricing | Guide to VMS: Machine Authority > Machines > Edit. Reference Section 4. |
| User asks about account access | Reference Section 2 and Section 7.3. Escalate password admin issues to Sandstar. |
| Hardware issue identified - by error code OR by the user describing a physical hardware problem (e.g. 'my lock is broken', 'the door won't latch', 'the camera is physically damaged') | Once all required case information has been collected and the issue is confirmed as hardware-related, inform the user that this requires hands-on service and state that you are escalating the case to a human support technician. Do not attempt further remote troubleshooting for confirmed hardware failures. |
| Issue not found in this document | Collect all case info and escalate to a human agent. Direct user to support@sandstar.com with full context. |