/
Punchout

Punchout

Below is the end to end process Punchout customers need to follow, with some notes, complete the process and indicate where an error occur to Straightsell support.

PunchOut - ERP Purchase Order Creation:

The first thing that should be done is to ensure the correct process is followed by the customer to generate the PO from the website catalogue via a PunchOut from their procurement system.

  • Launch PunchOut from the Procurement ERP software.

  • Add an item to the cart and open the cart.

  • Select a freight option in the shopping cart *

  • Select the “Order PunchOut” button in the cart to send the PO back to the Procurement ERP.

* This option may not may not be applicable based on customer specification.

Validation Tests Satisfied:

  1. Successful PunchOut from Procurement ERP to the website account i.e. passthrough login

  2. Cart has the requisite features for purchase order creation in Procurement ERP.

  3. Purchase order reception to Procurement ERP from the website via cXML.

Options - Purchase Order:

  • UOM - All line-items are sent to the PO with either of the below, based on the specific requirements of the customer:

    • ‘EA’ (or another valid Procurement ERP UOM e.g. CTN) is a hardcoded value for the UOM.

    • UOM value is retrieved from either a custom form or item field

  • Freight - All line-items are sent to the PO with either of the below, based on the specific requirements of the customer:

    • No freight line item

    • Freight line item of $0.00 (or other hard-coded value)

    • Freight line item with standard calculated freight value.

  • Tax - All line-items are sent to the PO with a tax code of either:

    • “GST” - if the item in the CMS has 'Tax = 10'.

    • “FREE” - if the item in the CMS has ‘Tax = 0’.

  • UNSPSC - All line-items are sent to the PO with either of the below, based on the specific requirements of the customer:

    • A specific value is a hardcoded value for the UOM.

    • UNSPSC value is retrieved from either a custom form or item field

Options - Catalogue:

  • Item Filtering- The items displayed to the PunchOut user with either of the below, based on the specific requirements of the customer:

    • No filtering, all catalogue items are available

    • Filtered set of items from the global catalogue:

      • Derived from a form specific to the:

        • Account manager user ID

        • Account manager user ID + Buyer ref.

      • Derived from a custom field for all items

  • Pricing - The item prices displayed to the PunchOut user with either of the below, based on the specific requirements of the customer:

    • Use of one Buyer Ref value to derive prices for all PunchOut sites (one or more)

    • Mapping of each PunchOut site to a specific Buyer (debtor)

EDI - Straightsell CMS Web Order Creation:

Once the purchase order approval is complete via Procurement (without change) an order should be shown against the debtor and subsequently downloaded by the Integration.

Validation Tests Satisfied - EDI:

  1. Web order creation from Procurement ERP to the website CMS via cXML.

  2. Correct routing of Procurement ERP site to the Accounting ERP debtor

Troubleshooting Notes:

  • If the Punchout Users manually or automatically change the PO product codes there will be issues.

  • If the Punchout Users use the incorrect site code the web order creation will either fail or be created for the wrong debtor

Error Handling & Support Escalation

Critical Error Notes:

  • Punchout Fail from ERP to Website:

    • Confirm correct PunchOut Specific URL with customer

    • Confirm correct username (NetworkID) and password (SharedSecret) for account manager user with customer

    • Confirm correct endpoinmt URL (…/loginRequest)

    • Has DNS been created for the PunchOut Specific URL?

  • Manual Edits: If users manually change Product Codes or Prices within their Procurement ERP after the PunchOut but before approval, the inbound Web Order will likely fail or be "Held for Review."

  • Site Code Mismatch: If the Procurement ERP sends an incorrect AddressID or Site Code, the order will fail to route to the correct Accounting ERP debtor.

  • Unit of Measure (UOM): If the cXML payload contains a UOM not supported by the Procurement ERP the purchase order will not be created