Warehouse Docs / Support
๐Ÿ“˜ CargoPRO docs

Support

How to reach the CargoPRO team, what to send with your ticket, and what to expect once it is open.

Contact channels

๐ŸŽซ

Support ticket portal

The fastest route: every request gets a tracked ticket with a full history, and you can reply by email as it progresses.

https://support.devtrixx.com

โœ‰๏ธ

Email

Prefer email? Write to the same team at support@devtrixx.com โ€” include the same details listed below so nothing is lost in the first reply.

What to include in a ticket

A ticket with the right details is usually solved in the first reply. Before sending, collect:

IncludeWhy it helps
VersionsThe warehouse app version (from pubspec.yaml) and your CargoPRO admin panel version (shown in its sidebar footer).
Account roleWhether you signed in as a Manager or a Warehouse user, and which warehouse was selected.
Steps to reproduceNumbered steps from a known state ("log in โ†’ open Shipments โ†’ change status to X"), so the team can replay them exactly.
Screenshots or recordingOf the error message, the screen just before it, and (for apps) the device you used.
Laravel log excerptThe stack trace around the error timestamp from storage/logs/laravel.log on the server.
DeviceAndroid or iOS version and the device model.

To pull the relevant lines from the website's log over SSH:

tail -n 100 storage/logs/laravel.log
Never send passwords or live keys Blur passwords, API keys and customer personal data in screenshots โ€” a description of the config entry is enough.

What support covers

โœ…

Covered

Installation and upgrade problems, bugs and errors in the delivered code, questions about documented features and configuration, and license or account access issues.

๐Ÿ› ๏ธ

Custom development

Customizations and new features, changes beyond the documented settings, custom integrations, and third-party hosting or server-administration issues. Send the scope in a ticket and the team will get back to you with a quote.

Response times

What to expect The team answers during business hours, typically within 24โ€“48 hours. Investigations that need to be reproduced on a clean install can take a little longer โ€” you will see the progress on the ticket. These times are guidance, not a guaranteed service-level agreement.

Before you open a ticket

Check Troubleshooting first The most common problems โ€” refused logins, empty queues, missing permissions and builds pointing at the wrong server โ€” are answered in Troubleshooting.