This project brings shipping rate calculation to your ecommerce app using the EasyPost API. It is published as a nuget code library and conforms to a standard shipping interface published in the base library OrderCloud.Catalyst.
- If you haven't, please review Order Checkout Integration Event focusing on the ShippingRates event. In short, a webhook from the platform makes a request to a solution-custom API route that contains logic for estimating shipping rates.
- This library can be installed in the context of a .NET API project that responds to those webhooks. If you already have a .NET API project, great. If not, you can follow this guide. After you have published your API, you will need to configure OrderCloud to point its Integration Event webhooks at your API.
- In your .NET project, add the OrderCloud.Integrations.Shipping.EasyPost nuget package with either the Visual Studio UI or the dotnet CLI.
dotnet add package OrderCloud.Integrations.Shipping.EasyPost
You will need these configuration data points to authneticate to the EasyPost API - ApiKey, BaseUrl, and CarrierAccountIDs. Create an account with EasyPost and get these from the admin portal.
var easyPostService = new EasyPostService(new EasyPostConfig()
{
BaseUrl = "https://api.easypost.com/v2",
ApiKey = "...",
CarrierAccountIDs = new List<string> { "...", "..."}
});
For efficient use of compute resources and clean code, create 1 EasyPostCommand object and make it available throughout your project using inversion of control dependency injection.
services.AddSingleton<IShippingRatesCalculator>(easyPostService);
Notice that IShippingRatesCalculator is not specific to EasyPost. It is general to shipping rates and comes from the upstream OrderCloud.Catalyst package.
Create routes that respond to the OrderCloud platform's Integration Event webhooks. Inject the shipping interface IShippingRatesCalculator and use it within the logic of the route. It is not recommended to rely directly on EasyPostService anywhere. The layer of abstraction that IShippingRatesCalculator provides decouples your code from EasyPost as a specific provider and hides some internal complexity.
public class CheckoutIntegrationEventController : CatalystController
{
private readonly IShippingRatesCalculator _shipMethodCalculator;
public CheckoutIntegrationEventController(IShippingRatesCalculator shipMethodCalculator)
{
// Inject interface. Implementation will depend on how services were registered, EasyPostService in this case.
_shipMethodCalculator = shipMethodCalculator;
}
....
[HttpPost, Route("shippingrates")] // route and method specified by OrderCloud platform
[OrderCloudWebhookAuth] // Security feature to verifiy request came from Ordercloud.
public async Task<ShipEstimateResponse> EstimateShippingRates([FromBody] OrderCalculatePayload<CheckoutConfig> payload)
{
var response = new ShipEstimateResponse();
// containerization logic - how should lineItem quantities be boxed into a set of shipped packages?
response.ShipEstimates = new List<ShipEstimate> { ... }
var packages = response.ShipEstimates.Select(se => MapToPackages(response.ShipEstimates));
// use the interface
List<List<ShipMethod> rates = await _shipMethodCalculator.CalculateShipMethodsAsync(packages);
for (var i = 0; i<response.ShipEstimates.Count; i++)
{
response.ShipEstimates[0].ShipMethods = rates[0]
}
return response;
}
}
This library also supports more complex cases that require mulitple shipping accounts with different credentials. For example, in a franchise business model where each location is independent but all sell on one ecommerce solution. In that case, still inject one instance of EasyPostService
exactly as above. You can provide empty strings for the fields. However, when you call methods on the interfaces, provide the optional configOverride
parameter.
EasyPostConfig configOverride = await FetchShippingAccountCredentials(supplierID);
var packages = new List<ShipPackage>() { ... }
List<List<ShipMethods> rates = await _shipMethodCalculator.CalculateShipMethodsAsync(packages, configOverride);