Assumptions

General Assumptions
  1. The SOAP Shipping API for Metapack Delivery Manager will be used.

  2. All Metapack calls are direct SOAP requests in XML format and do not go through middleware.

  3. The carrier service (the combination of carrierCode and carrierServiceCode in Metapack) identified by Delivery Manager during a Rate Shop is mapped to a Manhattan Ship Via.

    Note

    Each combination of carrierCode and carrierServiceCode must be mapped to a distinct Ship Via, with the carrier being marked as 'external' in WMOS/MAWM.

  4. The carrierCode and carrierServiceCode values from Delivery Manager will be no longer than 50 characters.

  5. Manhattan will not save the cost data returned from a Rate Shop as these are estimates.

  6. MAO and MAWM make a Consignment call to Metapack Delivery Manager for each individual parcel and there will not be multiple parcels within a Consignment. It is not in scope to have multiple package shipments, master tracking numbers, or X of Y processing.

  7. The shipping labels provided by Metapack meet the language and legal requirements of shipping in Europe after Brexit. There is no requirement by Manhattan to translate any shipping labels.

  8. Metapack shipping labels are generated in the standard 4" x 6" label size. Manhattan does not perform any label resizing.

  9. The Metapack shipping document file format for the Print call is configurable in Manhattan in order for each application to support its base functionality.

    1. It is in scope for a WMOS/MAWM shipping label to be configured as ZPL format with a 4" x 6" size. It is in scope for a MAO shipping label to be configured as PDF format with a 4" x 6" size. If alternative shipping label configurations are required, then additional changes need to be specified and taken up by the respective project teams.

    2. It is in scope for a WMOS/MAWM customs form to be configured as PDF format. If alternative printer configurations are required, then additional changes need to be specified and taken up by the respective project teams.

    3. It is out of scope to generate the customs form in MAO. If a customs form is required in MAO, then additional changes need to be specified and taken up by the respective project teams.

  10. In MAO/MAWM, after a successful Shipping call has been made to Metapack Delivery Manager to create a Consignment, no edits to to add or remove parcels are permitted. It is out of scope to use appendParcelsToConsignment.

    Note

    The WMOS EPI integration allows the use of appendParcelsToConsignment.

  11. The Unit of Measure sent to Metapack is derived from the respective Manhattan Master UOM Item. Manhattan does not convert UOM in the request to Delivery Manager. Metapack supports both metric and imperial UOM.

  12. Parcel dimensions must be sent to Delivery Manager, although it does accept values of “0”.

  13. Manhattan can only send a Void Shipment request to Metapack if the Consignment has not yet been manifested.

  14. MAO/MAWM sends a request to MetaPack to mark shipments as ready to manifest based on a scheduled process and a configurable remorse period.

  15. If the shipping label call to the carrier fails, the user has the option to retry from the User Interface. This is applicable for integration with Metapack for all of Rate Shopping, Shipping and Printing.

  16. Each Manhattan-enabled Fulfillment Location has a unique Metapack customer number.

  17. Each Manhattan customer is responsible for configuring facility account information for each location.

  18. The customer is responsible for supplying appropriate label stock and for any printer configurations both inside and outside of Manhattan.

  19. Manhattan is responsible for marking the consignments as ready to manifest. The manifests will be sent on a scheduled basis by Metapack.

  20. Each customer is responsible for ensuring that the frequency of the Manifest process (as well as any additional manifests triggered on an ad hoc basis) is aligned with any billing limitations set by their respective carriers.

  21. Metapack Delivery Manager functionality re-evaluates the optimal shipping method during each of the Rate, Shipping and Print calls. It is therefore possible that Metapack can change the selected carrier for a Consignment between these calls. Because of this, Metapack expects the Rate Shop Ship Vias to always be sent in the Booking Code field of the API request to allow for re-evaluation to occur.

MAO Assumptions
  1. MAO SOF package weight includes the item weight only. MAO does not maintain the package weight (box/envelope).

  2. Metapack Delivery Manager supports moving the packages in each fulfillment to a status of 'shipped automatically’, i.e. without actual confirmation from the carrier that the package has been picked up. If confirmation from the carrier is required, then additional changes need to be specified and taken up by the respective project teams.

  3. MAO standard behaviour does not allow a user to cancel/void a package after it has been submitted via the UI screens. If voiding a package from the UI screens after it has already been submitted to Metapack is required, then additional changes need to be specified and taken up by the project teams.

    Note

    The Void call can be triggered from the back end in MAO if the user changes the shipping method after the Shipping call has been made to Metapack.

  4. Rate Shop capabilities are not standard behaviour in MAO. However, due to the nature of Metapack Delivery Manager, it is possible for Metapack to change the Ship Via in the Shipping and/or Print calls that are generated from MAO.

MAWM Assumptions
  1. Distribution Orders that require integration with Metapack will be marked by the host or integration layer with a Distribution Ship Via where the associated carrier is configured as an 'external' carrier. (This may not be necessary for a Rate Shop.)

  2. Only individual oLPNs are integrated with Metapack, not Pallets of oLPNs.

  3. An EPI Rate Shop will only be done during a routing wave or as part of the routing pipeline.

  4. In the 'golden flow', the EPI Shipping process (i.e. Consignment creation and allocation in Metapack Delivery Manager) is performed through UI-WM Pack Station or as part of the WM Mobile Packing transaction. In the event that the message fails, this is re-sent through the UI-oLPN>Weight & Manifest screen.

  5. An EPI Rate Shop works at the order level, and LPN level routing is not supported.

  6. Pick Up, Drop Off/Locker Services are outside the scope of this implementation.

  7. This solution will use the last updated user on the LPN to determine the most accurate print requestor for reprinting Customs documents/Commercial Invoices sent from Metapack.

    This allows the user who has manifested the oLPN to reprint the documents manually via the oLPN UI, which will call the appropriate print requestor associated with that user.

    For printing linked to the normal Pack Station flow (i.e. automatically printing documents after packing), the invoice will be printed at the Pack Station that was configured by the print requestor under the Printing Document Strategy.

  8. The MAWM oLPN package weight includes the item weight only. MAWM does not maintain the package weight (box/envelope).