This screen supports EasyPost only. It is separate from WooCommerce Shipping and from Admin → Fulfillment Methods → Shipping, where customer-facing shipping methods, prices, tax, and scheduling are configured. The current integration screen has Connect but no separate Test connection, Disconnect, carrier-account, ship-from address, rate, label, tracking, or postage-purchase controls. Do not promise those controls from this page.
Step by step
- Create or select the retailer’s own EasyPost account and obtain an EasyPost API key through the retailer’s approved credential process. Do not use a Centri developer account, another retailer’s key, a key copied from logs, or a credential supplied in chat/email.
- Confirm the active CentriPOS business and that you are authorized to change tenant-wide integrations. Go to Admin → Integrations → Shipping. Verify the page heading is Shipping and the provider card says EasyPost and EasyPost only. WooCommerce Shipping stays outside this workflow.
- Read the current status badge before changing anything. Also review Provider, Mode, Last verified, and any visible Last error. Capture the status and timestamp without exposing credentials so you can tell whether a new connection changed the state.
- Choose Mode deliberately. Use Test with a matching EasyPost test key while validating setup without real postage. Use Live only with the retailer’s live key and explicit approval for production shipping. The selected mode and key must belong together; choosing Live does not convert a test key.
- Paste the retailer-owned EasyPost API key into the password field. The existing key is not displayed back to the browser. Re-entering a key and choosing Connect is a credential replacement/connection action, not a harmless status refresh.
- Choose Connect once and wait. CentriPOS sends the tenant, trimmed key, selected mode, and account label EasyPost to the secure shipping connection service. If the field is blank, the page shows Enter an EasyPost API key.
- On success, wait for EasyPost connected. The key field clears and the status query refreshes. Confirm the status badge, stored Mode, and Last verified time changed as expected. A status of connected or test receives the active badge styling; read the actual text rather than inferring production readiness from color.
- If connection fails, read the displayed error or Last error. Recheck key environment, ownership, revocation/permissions, selected mode, tenant context, and service availability. Do not repeatedly paste credentials or switch to Live merely to make a test failure disappear.
- Configure the customer-visible shipping choices separately in Admin → Fulfillment Methods → Shipping. Define only the enabled methods, names, base prices, tax behavior, and schedule/capacity rules the business actually offers. Connecting EasyPost does not create those choices or a ship-from address on this page.
- Run an authorized end-to-end test from the actual shipping workflow after both configuration areas are ready. In Test mode, use a controlled noncustomer test address/order and confirm the correct business/location context and expected provider behavior. In Live mode, obtain approval before any action that could buy postage. The connection page itself does not provide a rate or label test button.
- Verify downstream evidence only where the relevant shipping workflow exposes it: correct ship-to and intended ship-from context, selected shipping method, rate/postage environment, label/tracking identity, and fulfillment/receipt record. Do not assume Last verified proves a particular shipment, carrier, label, or tracking event.
- If production behavior is wrong, stop live postage actions and report the tenant, mode, status, Last verified, Last error, affected workflow, time, and privacy-safe identifiers. Never include the EasyPost API key, full customer address, or unredacted label.
Screen and contract reference
| Control or area | What it means |
|---|---|
| EasyPost | Only provider available on the CentriPOS Shipping integration page. Retailers use their own account; CentriPOS does not resell postage. |
| Status badge | Current connection state returned by the server, such as Not connected, test, connected, or another status string. |
| Provider | Displays EasyPost only; it is not a carrier selector. |
| Mode summary | Stored mode returned by the connection status, or Not set. |
| Last verified | Last server-reported verification timestamp; it does not prove a specific rate, label, or shipment. |
| Last error | Most recent connection/service error returned for this integration when present. |
| Mode → Test | Stores a test-mode connection; pair it with the retailer’s EasyPost test key. |
| Mode → Live | Stores a production-mode connection; pair it with the retailer’s live key and approval for postage-capable workflows. |
| EasyPost API key | Password-style input for a retailer-owned key. Existing secret material is not displayed in the status card. |
| Connect | Saves/replaces the connection using the selected mode and entered key; no separate Test connection button exists on this screen. |
| EasyPost connected | Save succeeded, key input clears, and status is refetched. |
| WooCommerce separation | WooCommerce Shipping is configured and operated outside the built-in EasyPost workflow. |
| Fulfillment Methods → Shipping | Separate place for enabled customer-visible shipping methods, names, base prices, tax treatment, and shipping scheduling. |
| Not on this screen | No Disconnect, carrier account, package preset, ship-from address, rate request, label purchase/void, tracking, or postage history controls are exposed here. |
| No exact screenshot | The approved Amelia Grant Harbor & Hearth manifest contains an Integrations overview capture but no exact Shipping/EasyPost credential page. This guide intentionally avoids a mismatched screenshot and never depicts a real key. |
Expected result
The authorized carrier or shipping service returns the intended rates and labels for a controlled shipment and writes tracking back to the correct fulfillment record.
Troubleshooting
- Confirm you are changing the intended business and location before saving.
- Record the previous setting when a change affects live selling, payments, tax, or integrations.
- Use a controlled test record after saving before rolling the setting out broadly.
CentriPOS API explorer · API Center administration