Forge is EasyPost's premier white-label platform designed for marketplaces, platforms, and 3PLs. Existing EasyPost Core customers may be eligible to upgrade to Forge. This article provides details on the upgrade process, integration requirements, account access, and feature differences between Core and Forge.
Upgrade Eligibility
Forge is currently in beta and available to select Centralized white-label customers. To check eligibility or join the waitlist, contact EasyPost Sales.
Integration and Account Changes
Q: Does upgrading to Forge require integration changes?
A: No, upgrading to Forge does not require changes to an existing integration. API keys, webhooks, child or referral customer subaccounts, and other account data will carry over automatically.
Q: Will a new account, username, or password be required?
A: No, upgrading to Forge does not require creating a new account or changing login credentials. Once Forge is enabled, the existing EasyPost account can be used to access the upgraded features. However, agents must be re-invited to Forge by an account administrator.
Q: What account data will not carry over during the upgrade?
A: Agents invited to the EasyPost Core account will not be included in the upgrade. Forge has different member roles and permissions compared to the Core platform. Agents must be invited separately through the Forge Members page.
Feature Differences Between Core and Forge
Q: Are there EasyPost Core features that are not available in Forge?
A: Yes, Forge is designed for businesses that provide shipping solutions to end users, whereas the Core dashboard serves retailers, brands, and shippers creating shipping labels for their own operations. Due to these differences, certain features are only available in EasyPost Core.
Features exclusive to EasyPost Core:
- Create Label & Bulk Create Label Tools
- Sender Addresses Tool
- Schedule Pickup Tool
- Luma
Managing Core and Forge Access
Q: Can the Core Dashboard access be retained after upgrading to Forge?
A: Yes, the Core Dashboard access can be retained after upgrading to Forge. Accounts with both Core and Forge enabled can navigate between both products. Usage, billing charges, and activity will be reflected in both platforms since they share the same EasyPost account.
Q: How can separate billing and API usage tracking be managed for Forge?
A: To track Forge activity (e.g., label purchases, rating calls) separately from Core activity, a new EasyPost account is required. At this time, it is not possible to have different payment methods or subscriptions for each product under the same EasyPost account.