Skip to main content

​
Manage cable and accessory orders

This internal article is a support reference for ordering extension cables, Y-cables, and replacement DataLogger hardware on behalf of a customer through the BitBrew Fulfillment API.

​
Before you start

  • This article is for Servinix support staff only. Customers cannot place accessory orders directly from the portal.
  • You need BitBrew API credentials and access to the fulfillment endpoint.
  • Confirm the customer’s account ID, shipping address, and the specific cable or accessory needed before placing an order.
  • Identify the correct cable type by checking the vehicle class and port type. Common types are:
    • Standard OBD II — Class 1–3 vehicles, model year 1996 and later.
    • 6-pin — medium-duty vehicles (Class 4–6) with a 6-pin Deutsch port.
    • 9-pin — heavy-duty vehicles (Class 7–8) with a 9-pin Deutsch port.
    • Y-cable — used when the OBD II port is obstructed and requires an extension.

​
Steps

  1. Confirm with the customer which accessory they need and verify their shipping address in the Servinix account record.
  2. Log in to the BitBrew Fulfillment portal or use the BitBrew Fulfillment API with your support credentials.
  3. Create a fulfillment order with the following details:
    • Customer account ID — from the Servinix tenant record.
    • SKU — the part number for the cable or accessory (OBD II cable, 6-pin cable, 9-pin cable, Y-cable, or replacement DataLogger unit).
    • Shipping address — confirmed with the customer.
    • Quantity — number of units needed.
  4. Submit the order. Danlaw processes fulfillment orders and ships directly to the customer address.
  5. Record the BitBrew order ID in the customer’s support ticket for tracking.
  6. Notify the customer of the expected shipping timeline (typically 3–5 business days once the order is accepted by Danlaw).

​
Result / verify

A confirmed order ID from BitBrew indicates the order was accepted. Follow up after 2 business days if no shipping confirmation has been issued. Check the fulfillment status using the BitBrew order ID.

​
Troubleshooting

  • Order rejected by BitBrew API. Verify the customer account ID and that the SKU is valid. Contact the BitBrew support channel if the issue persists.
  • Customer received the wrong cable. Log an RMA and initiate a replacement order with the correct SKU. See Device installed but wrong cable used.
  • No shipping update after 5 business days. Escalate to the Danlaw logistics contact listed in the Escalation path article.