Core points

• Use abstraction layers to integrate multiple transport APIs (UPS, FedEx, USPS) into your e-commerce platform, providing a unified interface for a variety of transport operations.
• First set up the shipping provider account and obtain the necessary API keys and documentation to ensure compliance with the shipping provider's guidelines and procedures.
• Define and manage goods and parcels through object classes (Shipment and Package) standardized in the code, which simplifies the handling of different transport parameters and requirements.
• Implement the shipper plug-in to interact with a specific shipping API, so that rates and shipping tags are obtained without changing the core application code.
• Train errors calmly and protect abstraction layers to protect sensitive data, ensuring your e-commerce platform provides customers with reliable and secure shipping options.

Your new custom e-commerce store is almost done. The only thing left is figuring out how to calculate the customer's shipping fee. You don't want to use a standard flat rate for each address because you know you'll charge some customers too much and, more importantly, too low fees for others. Wouldn't it be great if shipping costs can be calculated based on the weight/size and destination of the item? Maybe you can even offer an accurate price quote for overnight delivery! You have a UPS account and you have checked their API, but it looks very complicated. If you hardcode your website to use APIs, you will have to do a lot of work if you need to change the shipper. Your cousin is a sales representative for FedEx and he swears he can get better rates for you with FedEx. Some of your customers only use PO boxes, so these items must be shipped via the post office. What should you do? You may have heard of database abstraction, a practice that allows you to use many different databases and a common set of commands. This is exactly what you can do here! To solve all of these problems, you can separate the transport task from the rest of the code and build an abstraction layer. Once done, it doesn't matter whether you ship your package via UPS, FedEx or USPS. The functions your core application will call will be exactly the same, which will make your life much easier!

UPS Getting Started

In this article, I will focus on using the UPS API, but by writing plugins for different shippers (such as FedEx or USPS), you can also access their services, and changes to core application code can be ignored Don't count. In order to get started with UPS, you need to register an online account at www.ups.com using your existing shipper number. Make sure to choose a username and password that you are willing to use for a while, as the API requires both for each call. Next, visit http://miracleart.cn/link/ebd74b9b3bfd11deb539e4242d95078b and register to access the UPS API. Here you will get your API key and be able to download documentation for different API packages. (Note: There are known issues with this section of the UPS website, and Chrome sometimes returns blank pages. You may need to use a different browser.) Remember that when you use the UPS API (or any of the shipping APIs), you Agree to abide by their rules and procedures. Be sure to review and obey them, especially before using your code for production environments, follow their instructions. Next, download or clone the shipping abstraction layer package from github.com/alexfraundorf-com/ship on GitHub and upload it to a server running PHP 5.3 or later. Open the include/config.php file. You need to enter your UPS details here, and the field names should be self-explanatory. Please note that the UPS shipper address must match the address recorded in the UPS account, otherwise an error will occur.

Define goods and parcels

Now define a Shipment object. On instantiation, it will accept an array containing the receiver information, and if it is different from the shipper information in our configuration file, you can select a shipping address.

// 創(chuàng)建一個(gè) Shipment 對(duì)象
$shipment = new ShipShipment($shipmentData);

Next, we need some details about what we are shipping. Let's create a Package object that accepts optional arrays of weight, package size, and some basic options such as description, whether signature is required, and insurance amount. Then add the newly instantiated Package(s) to the Shipment object. Software that simulates life makes sense: each parcel belongs to a cargo, and each cargo must contain at least one parcel.

// 創(chuàng)建一個(gè) Package 對(duì)象并將其添加到 Shipment（一個(gè)貨物可以有多個(gè)包裹）

// 此包裹重 24 磅，尺寸為 10 x 6 x 12 英寸，保險(xiǎn)價(jià)值為 274.95 美元，并且需要簽名
$package1 = new ShipPackage(
    24,
    array(10, 6, 12),
    array(
        'signature_required' => true,
        'insured_amount' => 274.95
    )
);
$shipment->addPackage($package1);

// 重量和尺寸可以是整數(shù)或浮點(diǎn)數(shù)，
// 盡管 UPS 總是向上舍入到下一個(gè)整數(shù)。
// 此包裹重 11.34 磅，尺寸為
// 14.2 x 16.8 x 26.34 英寸
$package2 = new ShipPackage(
    11.34,
    array(14.2, 16.8, 26.34)
);
$shipment->addPackage($package2);

(The following content is a simplification and rewriting of the "Behind the Curtain" chapter in the original text, avoiding duplication of redundant information and maintaining the integrity of key information)

Shipment object details: The Awsp/Ship/Shipment.php object in Shipment stores the receiver information (and optional shipper information) and includes the addPackage() and getPackages() methods to manage the package.

Package object details: The object in Awsp/Ship/Package.php stores the package weight, size and optional parameters, automatically sorts the dimensions by length, width and height, and calculates the package size (length, perimeter) . Package

Shipman Plugin: Plugin (e.g. ShipUps) implements the ShipperInterface interface, providing a unified getRate() (get freight) and createLabel() (create tags) method.

Get shipping: Get shipping by calling $ups->getRate() and use the try/catch block to handle the error. The result is returned as a RateResponse object, containing the status and details of each shipping option.

Create a shipping tag: Call $ups->createLabel() Create a shipping tag, and the result is returned as a LabelResponse object, containing the status, total cost, tracking number, and base-64-encoded tag image.

Detailed explanation of RateResponse object: The Awsp/Ship/RateResponse.php object in RateResponse stores freight data in standardized format, including status, service option arrays, etc.

Detailed explanation of LabelResponse object: The Awsp/Ship/LabelResponse.php object in LabelResponse stores label data in standardized format, including status, total cost, label array, etc.

Detailed explanation of UPS Shipmenter Plugin: Awsp/Ship/Ups.php Convert standardized Package and Shipment objects to formats that are understandable by the UPS API, communicate with the SOAP API, and convert the response to Standardized RateResponse or LabelResponse objects.

Summary: With the abstraction layer, you can easily use the UPS API or other shipper's API, simplifying interaction with different APIs and reducing maintenance costs. If you need to integrate USPS, it is recommended to use USPS approved vendors such as stamps.com instead of directly using the official USPS API.

(The original FAQs part has been streamlined, retaining core information and avoiding duplication)

FAQs (FAQs)

• What is the purpose of the abstract transportation API? Simplifies the process of integrating various transportation services into a single application, providing a unified interface and reducing complexity.
• How does the abstract transportation API benefit your business? Seamlessly integrate multiple shipping options to improve customer satisfaction, simplify operations, automate processes, and reduce errors.
• What are the challenges of the abstract transportation API? The structural, functional and documentation differences of different APIs require flexible and powerful abstraction layers and require continuous maintenance to cope with API updates.
• How to deal with errors in the abstract transport API? Implement a robust error handling mechanism, verify API responses, catch exceptions, and provide meaningful error messages.
• Can you use a third-party library to abstract the shipping API? Yes, but requires careful evaluation to ensure that specific needs are met and actively maintained.
• How to test abstraction layers? Write unit tests and integration tests and use mock APIs to test.
• How to deal with rate limiting in abstract transport API? Implement mechanisms to handle rate limits, such as retrying a request or reducing the request rate.
• How to protect abstract layers? Implement security measures such as encrypting sensitive data, using secure communication protocols, and periodically updates to fix security vulnerabilities.
• How to deal with version control in the abstract transport API? Design abstraction layers to handle different API versions, such as using version-specific endpoints or parameters.
• How to keep abstraction layers in sync with changes in the shipping API? Regularly monitor shipping API changes, subscribe to API updates, and quickly test and deploy updates.

The above is the detailed content of PHP Master | Abstracting Shipping APIs. For more information, please follow other related articles on the PHP Chinese website!