This article outlines a simple, repeatable process for activating a new carrier in Pacejet — from initial planning through sandbox testing and final go‑live in production.
1. Plan your activation and go-live
Before you touch any settings, define your approach:
Which environments will you use? Sandbox and then production.
Who is involved? Pacejet admin, carrier/IT contact, warehouse lead, key end users, ERP admin.
What is your success criteria? For example: “Carrier X can rate, ship, and update ERP correctly for parcels and LTL by [date].”
Document at least:
Scope (which carrier services, which locations, which business units).
Owners (who is responsible for testing, training, sign-off).
Timeline and go-live window (when you can safely cut over).
2. Sandbox activation and connection
You will first activate the carrier in Sandbox (SB).
-
Gather carrier credentials
API keys, account numbers, meter numbers, passwords, etc.
Any required pickup or billing account IDs.
-
Coordinate with your Pacejet representative
Provide the necessary credentials securely.
Confirm which Pacejet environment is your sandbox.
-
Activate the connection in Sandbox
Your Pacejet representative activates the connection in SB by running an implementation script with your credentials in test mode.
Below is an example activation screen for LTL carrier R&L with required values of API key, test mode, and pickup type.
The required information may vary by carrier and will be requested by your Pacejet representative.
3. Configure and test in Sandbox
Once the connection is live in SB, work through the following areas.
3.1 Decide Which Classes of Service to use
Clarify which Classes of Service you will use. All available Classes of Service will be available by default.
Service types (ground, 2-day, next-day, international, freight, etc.).
Any contract-specific or premium services (for example, guaranteed delivery times)
Visit the Setup --> Carrier page and click on the newly activated carrier. Visit the
Configure:
Service codes and descriptions.
Default service mappings for common shipment scenarios.
Any restrictions per location, customer, or shipment type.
3.2 Set up rate shopping rules
Decide how you want rate shopping to work with this new carrier:
Will this carrier always be available, or only for certain destinations, weights, or customers?
Should it be excluded from certain lanes or order types?
Typical steps:
Add the carrier to your rate shop groups.
Configure business rules such as include/exclude by destination, weight, customer, or shipping method.
Verify that rate shopping returns expected services, accurate pricing, and correct transit times where applicable.
3.3 Configure special options and mappings
Determine whether you need special configuration, such as:
Reference field mapping – map order or ERP fields (for example, PO#, customer reference, cost center) into carrier reference fields, label messages, or customs documents.
Accessorials and options – residential delivery, liftgate, inside delivery, Saturday delivery, and similar options.
Hazmat or special handling – hazmat flags, UN/NA numbers, packaging types, and limited quantity indicators.
International requirements – commercial invoice data, harmonized codes, Incoterms, and tax IDs.
Validate that required data is present and in the correct format, and that missing or invalid data is surfaced with meaningful errors before label creation.
3.4 Paperwork and label configuration
Decide which paperwork and labels you need for this carrier:
Shipping labels (standard carrier labels).
Packing lists or combined label/packing slip documents.
Bills of Lading (BOL) for freight.
Commercial invoices and customs documentation.
Any carrier-specific forms that may be required.
Run test shipments to verify that all required documents print automatically, with accurate and correctly formatted data.
3.5 ERP cross-references and updates
Ensure that your ERP integration is updated for the new carrier:
Map carrier and service codes between ERP and Pacejet.
Confirm how tracking numbers, freight charges, service names, and shipment status updates flow back into ERP.
Typical items:
Add or update ERP carrier and ship-via codes.
Configure cross-references in Pacejet (carrier and service mappings).
Verify that ERP orders can select the new carrier/service and that completed shipments push shipment method, freight cost, tracking information, and any required references.
4. Sandbox user acceptance testing (UAT)
Run structured UAT in Sandbox before you consider go-live.
Recommended scenarios:
Standard domestic shipment (your most common use case).
At least one edge case such as oversized or heavy shipments, residential vs. commercial addresses, or freight vs. parcel.
Any international or hazmat scenarios you support.
For each test, confirm that:
Rates return as expected, with no missing or unexpected services.
Selected services and options match the business scenario.
Labels and paperwork print correctly.
ERP receives expected updates, including tracking and costs.
Once UAT is complete, get formal sign-off from the business owner (for example, shipping or logistics manager) and, if needed, the ERP owner.
5. Training and go-live decision
Before production activation, decide on training and go-live approach:
Training – short walkthroughs for warehouse users on when to select this carrier, which services to choose for which scenarios, and how to read new labels and paperwork.
Go-live strategy – whether you will run a soft launch (limited scope) or a full launch, and what your fallback plan is.
6. Production activation and deployment
When you are ready to go live, repeat the connection step in Production.
Production credentials – confirm final, live carrier credentials (which may differ from test) and ensure all required IDs are production-ready.
Coordinate with your Pacejet representative – provide production credentials securely and specify that this is for production activation.
Activate the connection in Production – your Pacejet rep activates the carrier connection in Production by running the same implementation script with your production credentials, using
test=falseand production endpoints/settings.Apply configuration from Sandbox to Production – mirror enabled services, rate shopping rules, special mappings and options, paperwork/label settings, and ERP cross-references.
Run a small set of production test shipments (real or controlled orders) within your go-live window.
7. Post–go-live validation
After you start shipping in Production:
Monitor rate shopping results, label quality, paperwork accuracy, and ERP shipment updates.
Gather feedback from warehouse/shipping users and customer service.
Adjust rules, mappings, default services, and training materials as needed.