Ship smarter. From inside your ERP.

NovexERP integrates with the EasyPost API at https://api.easypost.com/v2 using Basic authentication. The integration requires a test key configured as EASYPOST_API_KEY_TEST — production keys are explicitly rejected during shipment creation for safety, ensuring you never accidentally generate live labels during development or testing. A separate production key (EASYPOST_API_KEY) is optional and used exclusively for tracker operations when needed.

Creating a shipment starts with defining the from and to addresses along with parcel dimensions and weight. NovexERP sends this data to EasyPost and receives back rates from multiple carriers including FedEx, UPS, USPS, and others configured on your EasyPost account. You compare prices, delivery estimates, and service levels side by side before selecting a rate. Address field validation runs before shipment creation, catching common errors like missing zip codes or invalid state abbreviations before they reach the carrier.

Purchasing a label generates a PDF or PNG file that is stored securely at /storage/shipping-labels/ outside the web root, preventing direct URL access to label files. Labels are served through an authenticated download endpoint that verifies the requesting user has appropriate permissions. The tracking number and carrier information are captured immediately and linked to the originating order and lot records automatically.

Tracking updates arrive via the EasyPost webhook endpoint at POST /api/webhooks/easypost. Each incoming payload is verified using the X-Hmac-Signature header to confirm it originated from EasyPost. Status updates flow through NovexERP's standard webhook processing pipeline with idempotent storage and retry logic. For full webhook processing details, see the Webhooks page.

Manual tracker creation supports entering tracking numbers from shipments created outside NovexERP, letting you consolidate all package tracking in one place. Label replacement handles situations where a label needs to be corrected — the original shipment is refunded and a new one created in a single operation, linked via the replaced_by_shipment_id field for full audit trail. A separate refund endpoint is available for cancellations. For shipment management workflows, see Shipping, and for Shopify fulfillment push, see Shopify.