Overview
Most courier and order integrations in Mintsoft include a Test Mode toggle that switches between testing and live environments. The Test Mode toggle controls which environment your integration connects to, ensuring you can safely test configurations without affecting live operations or incurring real charges. This Test Mode toggle should only be activated when instructed by the integration owner (for example, Shopify, eBay, Amazon, DPD, DHL, etc.) or the Mintsoft Support Team. It is important to note that not all integrations have a dedicated Sandbox API Endpoint, so please check with the integration owner first before continuing.
Test Mode (Enabled or Checked)
When Test Mode is enabled, your integration operates in a safe testing environment provided by the courier or order channel.
What Happens in Test Mode:
Connects to sandbox environment - Uses the provider's dedicated testing infrastructure.
Separate API endpoints - Sends requests to test-specific URLs, completely isolated from live systems.
Safe testing without consequences - Create shipments, import orders, and test workflows without affecting real operations.
Test credentials required - Most providers issue separate credentials specifically for their test environment.
Non-functional outputs - Labels, tracking numbers, and order confirmations generated are for testing purposes only and not valid for actual use.
No charges incurred - Testing activities do not result in billing or account charges.
When to Enable Test Mode:
Initial setup and configuration - Verify all settings work correctly before going live.
Testing new services or features - Safely explore new shipping services, order channels, or integration options.
Troubleshooting integration issues - Diagnose problems without impacting live order fulfilment.
Training staff - Familiarise warehouse teams with new processes using test data.
Validating changes - Test updates to configurations or settings before applying to production.
Production Mode (Disabled or Unchecked)
When Test Mode is disabled, your integration operates in the live production environment, handling real business transactions.
What Happens in Production Mode:
Connects to live environment - Uses the provider's production infrastructure for actual business operations.
Production API endpoints - Sends requests to live URLs that process real transactions.
Creates real shipments and orders - All actions have real-world consequences (packages ship, inventory updates, etc.).
Production credentials required - Requires live credentials issued for your production account.
Valid outputs - Labels, tracking numbers, and order data are real and functional.
Charges apply - Shipments, transactions, and API usage may incur real costs.
When to Use Production Mode:
After successful testing - Once you have verified Test Mode works correctly with all expected scenarios.
Live order fulfilment - Processing actual customer orders for dispatch.
Generating shipping labels - Creating valid labels for carriers to scan and track.
Importing real orders - Bringing in live sales data from your channels (Shopify, Amazon, eBay, etc.).
Day-to-day operations - All normal business activities after go-live.
Critical Points to Remember
Credential Mismatch
The most common configuration error occurs when the Test Mode setting does not match the type of credentials entered.
Problem:
Using test credentials with Production Mode enabled results in authentication failure.
Using production credentials with Test Mode enabled results in authentication failure.
Solution:
Always ensure your Test Mode setting matches your credential type:
Test credentials = Test Mode enabled (checked).
Production credentials = Test Mode disabled (unchecked).
Different API Endpoints
Test and Production modes use separate API endpoints (URLs) to connect to the provider's systems.
Why This Matters:
Test endpoints only accept test credentials and reject production credentials.
Production endpoints only accept production credentials and reject test credentials.
Sending requests to the wrong endpoint results in authentication errors, even if credentials are correct.
Common Error Messages:
"Invalid credentials".
"Authentication failed".
"Unauthorised access".
"HTTP 401" or "HTTP 403" errors.
These often indicate a Test Mode and credential mismatch rather than incorrect credentials.
Switching from Test Mode to Production Mode
When you are ready to go live, follow this checklist to safely transition from testing to production.
Step 1: Obtain Production Credentials
Contact your courier or order channel provider.
Request production API credentials (distinct from test credentials).
Verify you have all required fields (API keys, account numbers, passwords, tokens).
Step 2: Update Integration Configuration
Navigate to the integration settings in Mintsoft.
Replace test credentials with production credentials.
Do not mix credentials. Ensure all credential fields are updated to production values.
Double-check for typos or copy-paste errors.
Step 3: Disable Test Mode
Uncheck or disable the Test Mode toggle.
This switches the integration to production API endpoints.
Save the configuration changes.
Step 4: Verify Connection
Test with one shipment or order before processing bulk operations. Confirm the integration successfully:
Authenticates with the provider.
Creates a real shipment or imports real data.
Returns valid tracking numbers or order IDs.
Check for any error messages or warnings.
Step 5: Monitor Initial Operations
Watch the first few live transactions closely.
Verify charges appear correctly in your account.
Confirm labels, tracking, and data are valid.
Be ready to troubleshoot if issues arise.