=======================================================================================================================================================================================================


1) Magento order placed online

  • The default Magento order status becomes "Pending" or "Processing"

2) Order import locates pending orders created in Magento and transfers them to Counterpoint as an order


3) Orders Downloaded to CounterPoint that meet the status filter for new orders. Magento status is changed to "In CPSQL" (in_counterpoint)


4) Orders are processed within CounterPoint SQL using standard functionality until the order is released, creating a release ticket. 

    Release Tickets in CounterPoint are transferred to Magento as an Invoice (Partial and Full Releases are supported)

  • Release tickets in CounterPoint SQL are ready to be integrated as soon as they are saved, not posted. 
  • Partial quantity, Partial line and Full releases in CounterPoint SQL are supported and there is no limit to the number of partial releases that can be performed. 
  • Magento requires that 100% of the shipment fees collected on the order are released in full with the first invoice.
    • There is no ability in Magento to change this, therefore the integration supports this requirement.
  • In the case that an "Authorize Only" transaction cannot be captured, a notification can be configured so that packages for that shipment can be reclaimed before pickup by the carrier. 

5) Orders Partially Released in CounterPoint will be updated with a Magento status of Processing.


6) Optional: Tracking Numbers that have been added to CounterPoint SQL release tickets are transferred to Magento as a shipment.

7) Shipments and Tracking Numbers Uploaded.  Once all items on the order are shipped, Magento status marked as Complete.

  • Completed orders will be skipped during any processing.
  • The status can be changed to something other than Complete by editing the Magento CounterPoint SQL Integration.exe.CONFIG parameter:   <add key="MagentoStatusIn" value="complete" />

==========================================================================================================================================

Order Details:

Descriptions:

  • Line Item Description is the Description of the Item from the Magento Order

Shipping Charges:

  • Shipping Charges are recorded as Miscellaneous Charge 1
    • All Magento shipment types are supported and one or more Magento shipment types can be configured to link to a specified CounterPoint SQL Ship-Via Code.
    • All Magento carrier types are supported and one or more CounterPoint SQL Ship-Via codes can be configured to link to a specified Magento Carrier.
    • CounterPoint SQL misc charge taxes should match Magento's configuration.  For example, if misc charge 1 is not taxed in CounterPoint, then the shipping charges should not be taxed in Magento.

Prices:

  • All prices are recorded as a Price Overrides with Reason “MAGENTO"
    • This is to protect the transaction if it is ever necessary to edit the transaction before releasing it.
    • In some cases, CounterPoint SQL will automatically recalculate the price of items on order with item pricing.
    • Magento Item Discounts are received as the Calculated Price with the pre-discounted price received as Price-1.
    • If the Price of an item in Magento is changed, pricing is handled the same way a Price Override is in CounterPoint SQL.  Only new orders will honor the new price.

Coupons:

  • If a Coupon in Magento affects both  the price of an item, pricing is adjusted the same way a line item discount is applied.
    • Magento Line item and Transaction coupons are supported, however they can only be linked to a line discount CounterPoint SQL.  
      • CounterPoint SQL discount codes set up as fixed amounts or percents are not supported, and must be configured as prompted amounts or percents.
      • CounterPoint discount code must be valid online or both in-store and online.
      • Magento natively only allows one coupon code per purchase.  If multiple codes are used on the same order, a single discount code will be used to represent the combination of discounts.

Payment Methods:

  • All payment methods are supported and configured to link to a specified CounterPoint SQL "cash" type payment method and will generate a deposit payment and an adjoining deposit ticket, unless otherwise specified below.  The Magento payment order status must match the initial CPMI status defined for import in the app config.
    • Payments supported:
      • PayPal All-in-One Payment Solutions Supported using "Cash" payment type. 
      • PayPal Payment Gateways Supported using "Cash" payment type.
      • PayPal Express Checkout Supported using "Cash" payment type.
      • Authorize.net Direct Post Supported using "Cash" payment type.
        • Both payment actions of "Authorize and Capture" and "Authorize Only" are supported. 
          • When configured using "Authorize and Capture", Magento will process the card at the time of sale.
        • When configured using "Authorize Only", the integration will instruct Magento to capture the amount of the released CounterPoint SQL ticket from the pre-authorized transaction.
          • The remaining authorized amount will remain on the pending order in Magento.
      • Authorize.net Supported using "Cash" payment type.
        • Both payment actions of "Authorize and Capture" and "Authorize Only" are supported. 
          • When configured using "Authorize and Capture", Magento will process the card at the time of sale.
          • When configured using "Authorize Only", the integration will instruct Magento to capture the amount of the released CounterPoint SQL ticket from the pre-authorized transaction.
            • The remaining authorized amount will remain on the pending order in Magento.
      • Saved CC Supported using "Cash" payment type.
      • Check / Money Order Supported using "Cash" or "A/R" payment type.
      • Bank Transfer Payment Supported using "Cash" payment type.
      • Cash On Delivery Payment Supported using "Cash" or "A/R" payment type.
      • Though an order deposit and deposit ticket will be created in CounterPoint SQL, the store will be responsible for reconciling the receipt of manual payments.
  • When a "Cash" payment type is used, though an order deposit and deposit ticket will be created in CounterPoint SQL, the store will be responsible for reconciling the receipt of manual payments.
  • Zero Subtotal Checkout
    • When the Zero Subtotal Checkout payment method is used in Magento, it is not necessary to create a deposit payment nor adjoined deposit ticket in CounterPoint SQL. 
      • Normal release rules are enforced for a $0 order in CounterPoint SQL. 
      • Normal invoicing rules are enforced for invoicing a $0 order in Magento.
      • Shipping charges & payment for them will create a deposit ticket.
  • Purchase Order
    • When the purchase order payment method is opted in Magento, the PO # entered in Magento will become the CounterPoint SQL Customer PO # on the order and will not generate a deposit payment or deposit ticket.
      • Normal release rules are enforced for the order in CounterPoint SQL and will require a method of payment to be applied to the release ticket.
      • Normal invoicing rules are enforced in Magento, however the payment method selected in CounterPoint SQL will not be stored in Magento.
      • CounterPoint SQL supports PO numbers up to 20 characters in length.
  • A/R type payment handling
    • Although Magento payment methods can be linked to CounterPoint A/R payment types, the creation and updating of A/R type customers is not currently supported.
      • Therefore, orders with a payment type of A/R will not be imported unless the matching customer (linked by primary email address) exists beforehand.
      • To import orders with a payment type of A/R, a customer must first be created in both systems and configured in CounterPoint with a customer type of A/R.
      • The Purchase Order payment method must be mapped to CounterPoint's corresponding A/R paycode

Taxes:

  • All taxes are recorded as Tax Overrides with Reason “MAGENTO” 
    • All taxable sales recorded in Magento are recorded in CounterPoint SQL using a single specified "Tax Code".
    • All non-taxable sales recorded in Magento are recorded in CounterPoint SQL using a single  specified "No tax Code".
    • The taxable and non-taxable tax settings may be configured using the same CounterPoint SQL tax code
    • Taxes are received from Magento as a Tax Override (Reason Code "Magento") in order to protect the transaction in case it is ever edited in CounterPoint SQL.
    • In some cases, CounterPoint SQL will recalculate taxes based on the tax code if the order is edited.
    • CounterPoint SQL misc charge taxes should match Magento's configuration.  For example, if misc charge 1 is not taxed in CounterPoint, then the shipping charges should not be taxed in Magento.
    • To reconcile misc charges taxed from the total taxes reported collected in CounterPoint, Magento reporting must be used 

Gift Messages:

  • Gift Message Handling
    • When a transaction or item Gift Message is entered into Magento, a CounterPoint SQL transaction note with the ID "GIFT" will be created combining all Magento gift messages into one CounterPoint SQL note.
    • The Magento From and To fields are not available for capture by Magento, so the CPMI cannot provide this information in CounterPoint SQL.

Date / Time:

  • Transaction Date/Time handling
    • All transactions entered into Magento are recorded in Universal Time (or Greenwich Mean Time).
    • CPMI will correct the datetime upon import to the TimeZone configured on the workstation that hosts the Interface.

Edited Orders:

  • Magento Edited Orders:
    • Magento standard functionality creates a new order number for any manually edited orders.  Currently the CPMI does not support Magento edits using this method and the order will be imported as a new order.  
    • The original order must simply be cancelled in CounterPoint to avoid duplicates.

Tracking Numbers:

  • Tracking Numbers in CP (Option set to yes)
    • One shipment will be created in Magento for each Release Ticket created in CounterPoint SQL. 
    • The shipment is automatically generated when the first tracking number attached to the CounterPoint SQL release ticket is transferred to Magento. 
    • All tracking numbers entered for that CounterPoint SQL release ticket at that time or any time in the future will be assigned to the shipment for that CounterPoint SQL Release Ticket.
    • The Magento Order Status is Marked as Complete after all items have been released and tracking numbers entered into CounterPoint.
    • ** Tracking Numbers will only be imported into Magento if it is opted that tracking numbers will be entered into CounterPoint (or imported into CounterPoint from a carrier software). " 
    • Magento statuses may be renamed id desired  for customer-facing order information.  In_Counterpoint could be "Picking" or something similar; Completed could be "Shipped & Complete"
  • Tracking Numbers not in CP (Option set to no)
    • The order status in Magento will be updated to status selected in "MagentoStatusIn" field in app config when a release ticket is uploaded.  Label could be renamed "Pending shipping, etc"