Sales channels record what the shopper chose at checkout in the
requested-delivery-method field on the order
(x_studio_rdelivery_method). This table translates those values into
a service the 3PL accepts at order creation - the shape differs per
provider: Sprint takes a single Service Level string (Standard,
Express, NextDay), while ShipHero takes a shipping-lines object
(title, carrier and method).
Load Requested Methods does three things in one click: fetches the services the 3PL accepts into Accepted Services (Sprint: its fixed vocabulary; ShipHero: compiled from the orders already created on the account); collects every requested-method value already used on this company's orders into the mapping table; and auto-matches the two by name. Both tables stay hand-editable, so future services or checkout values can be added any time - re-running only adds and never overwrites an existing link.
At order push a mapped value wins. An unmapped value keeps the previous behaviour: Sprint sends the raw value (Standard when empty); ShipHero falls back to the carrier-mapping service and shows the raw requested value as the shipping title so the operator can see the intent.