# Troubleshoot Peoplevox
URL: https://support.starshipit.com/articles/90200000000502-troubleshoot-peoplevox
Canonical: https://support.starshipit.com/articles/90200000000502-troubleshoot-peoplevox
Markdown: https://support.starshipit.com/articles/90200000000502-troubleshoot-peoplevox.md
Updated: 2026-11-10

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Resolve Peoplevox label failures and missing package tracking, inspect event logs, and resend deleted orders.

Use this guide when Peoplevox cannot generate a label through Starshipit, package tracking is missing, or an expected order is missing.

## Only one package receives tracking

For consolidated shipments, tracking is returned when the despatch is complete. Check the final result before treating an earlier package response as a failure.

1. Check that both **Create packages using package details from Peoplevox orders** and **Consolidate multi-packages into one shipment** are enabled in Starshipit's Peoplevox settings.
2. Confirm Peoplevox is version `24.09-02` or later.
3. Compare each Peoplevox package's tracking number with its Starshipit label. Check whether the package layout changed or Peoplevox package identities were missing or ambiguous.
4. If Peoplevox has the correct tracking but a connected system does not, check that system's package tracking event subscription and processing with its integration provider.

Starshipit uses the first available tracking number for each tracking type when it cannot safely associate numbers with individual packages. Changing the settings does not reconstruct older shipments. Bring the affected despatch reference and package count to [Starshipit support](/ticket) if the results still differ. Avoid creating another shipment just to retry the tracking update.

## A failover label prints

A failover label usually means the courier rejected the shipment because of an address or order-data error.

1. Find the affected order in Starshipit.
2. Correct the address or other reported error.
3. In Peoplevox, find the despatch and click **Print**.
4. Click **Print** next to the package.
5. Confirm the shipping label and tracking number are returned to Peoplevox.

## Check Peoplevox event logs

1. In Peoplevox, switch to the **Integration** view.
2. Select **Event Logs**.
3. Find the request for the affected despatch.
4. Review the Starshipit API response for the specific error.

![Peoplevox Integration view](/uploads/articles/integrations/inventory-warehouse-retail-management/peoplevox-integration/image_9301341445135.png)

![Peoplevox Event Logs tab](/uploads/articles/integrations/inventory-warehouse-retail-management/peoplevox-integration/image_9301341454863.png)

:::note
The message `Carrier Integration could not matched print Request: - 1` is common and can usually be ignored when labels otherwise generate successfully.
:::

## An order was deleted from Starshipit

Peoplevox pushes orders into Starshipit. If an order is deleted from Starshipit, resend it from Peoplevox rather than running a Starshipit import.
