How to fix BRT errors
Here's what to do when a known incident prevents you from creating BRT labels.
Are your BRT labels failing to generate, or is BRT tracking not updating on Amazon? Here's how to investigate tracking issues and what to do if Support confirms a known label-creation incident.
Known BRT label-creation incidents and connection-reset errors
You may see a connection-reset message such as cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104.
📌 Note: If Support confirms that your error is part of a known incident, do not assume that your BRT credentials or the recipient's address are incorrect. Follow the incident updates rather than changing these details based on the connection error alone.
Check the ShippyPro Status page for real-time incident updates.
Once resolution is confirmed, you can resume shipping and correct affected orders. Follow How can I fix orders in error? for the correction procedure.
If you need to check whether your error is part of a known incident, or it persists after resolution is confirmed, see How to get in touch with ShippyPro Support Team.
For other BRT errors, consult the BRT troubleshooting guide in Italian.
Why is BRT tracking awaiting pickup or unavailable on Amazon?
Does your BRT tracking remain awaiting pickup, update only after several days, or become unavailable on Amazon? Start by checking which tracking code is recorded for the shipment.
ShippyPro forwards to Amazon the tracking code received from BRT when you create the shipment.
- Compare the code printed on the physical BRT label with the codes recorded in ShippyPro and Amazon.
- If it is still unclear whether Amazon recognizes that code, ask BRT which tracking code Amazon accepts for external monitoring.
- Once BRT confirms the code, ask ShippyPro Support to verify whether it is transmitting that code to Amazon.
📌 Note: Matching codes on the label, in ShippyPro and on Amazon do not establish why Amazon tracking is stalled. One hypothesis is that BRT generates two distinct tracking codes and Amazon recognizes a different one from the code transmitted. This requires confirmation from BRT: it is not a verified cause or a guaranteed fix.
For existing BRT tracking-number explanations, see Why does my BRT/Bartolini tracking start with SHP? The explanation is available in Italian. For integration setup, see How to connect Amazon v2 to ShippyPro.
When you contact ShippyPro Support, include BRT's confirmation, the code printed on the physical label or a photo of the label, and the associated order reference. If you find differences between the label and the records in ShippyPro or Amazon, include one or two additional examples.