If UltraCart encounters 50 consecutive errors from your server, it will disable the XML postback and email you. The transmissions will queue up until you edit your XML Postback configuration.

After reviewing the logs to determine the cause of the errors. To restart the processing of the queued orders, re-save the XML PostBack settings (Click the save button on the XML Postback configuration page.)

If you need the complete refunds to report the item ID's in the order, contact UltraCart by emailing support@ultracart.com stating your UltraCart MerchantID requesting that we enable the merchant property "XML Postback - Skip Adjustment for Refund". 

With this property is enabled, it will prevent refunded items from being removed from the XML postback, so you will see these items in your refund transaction XML packet.

Pay close attention to these optional elements that will indicate the refunding of the item:

• quantity_refunded
• total_refunded 

 A: The XML Postback transmissions are always a single order only.

 A: Yes, if they are present on the order then they are populated in the XML.  We don't populate empty elements for these fields though.  The element names are:

• special_instructions
• comments
• gift_message
• merchant_notes
  
  Please consult the XML Schema for a full description of the XML document structure.

 A: When your server returns a 500 error it means that the code on the other side (your side) has experience an unhandled error condition.  Typically that is a null pointer exception, database error, etc.  Please check your server logs for further details.

 A: XML postback does not recognize that it's held in the fulfillment transmission queue. The state of the order will be the shipping department so the current_stage element in the XML will read "SD".
    (NOTE: The XML will not register a new stage change until the order is either marked as shipped (which would trigger the XML stage "CO" or if the order were to be marked as "Rejected" then the XML would read "REJ")

A: In this situation, the stage changes from "AR" to "SD" and an XML postback will occur if you have it configured to send one when stages change.

 A: If the order is an auto order there will be these elements in the XML:

• auto_order_code
• auto_order_original_order_id

 A: Yes. The auto order configuration now has a separate configuration field "Transmit Auto Order Status to URL when auto order changes" for auto orders. 
     If configured, auto order cancellations will trigger a XML Postback transmission when status changes.

 A: UltraCart will disable the XML postback after 50 consecutive non HTTP 200 responses. UltraCart will continue to queue up the requests and will send them only once the merchant goes back into the XMP Postback configuration page and saves the configuration, which reset the hold and releases the queued orders from immediate transmission. (So for example if you were doing some database maintenance for an hour that interrupted the transmissions, you would need to resave the settings to get things processing again.)

 A: XML postback requests are added to a queue when the order is placed.  The queue is processed asynchronously by a background job once a minute.  The number of postbacks that can be handled each cycle depends upon the throughput speed of the remote servers.  Performing the postbacks in the background makes sure a merchant's slow or unresponsive server does not destabilize the front end of the platform.  If there is a large spike in orders to the platform, the number of cycles to clear out the postback queue will vary.

 A: The complete XSD schema file for the order XML postback is located here: http://secure.ultracart.com/xml/ultracart.xsd

 A: Yes. To configure more than one URL into one of the URL configuration fields, simply separate each URL with a SPACE. 

PLEASE NOTE: Both endpoints must be able to deal with duplicates. If any endpoint fails, the postback is marked as a failure and when retried, each endpoint gets the postback again.    

There is quite a bit of order information in the XML postback, including customer data and the custom fields 1-7.

On an order XML postback there is an element for the auto_order information. Inside that element there is a field for auto_order_original_order_id. If that is the same as the order_id in the XML document then this is the original order in the auto order sequence. If it's different then it's a rebill.

Orders go through one URL and auto order status information through another. They can be the same URL if you want to configure it that way and just teach the one script to parse the XML document and then look at the content differently.

There is not a schema file for this yet, but the easiest thing to do is configure a dummy URL, let the auto order XML postback fire, and then check the log under the XML postback configuration to see a copy of the document it tried to send.