Help with your order
Support runs by email. Most of what people write in about is answered below, faster than a reply would reach you, and the rest tells you exactly what to put in the message.
Frequently asked questions
I have paid. Where is my download?
It goes to the email address you typed at checkout. Check that inbox and its spam folder first. A mistyped address is the usual culprit and we can resend to the right one, so tell us what you meant to type. If nothing arrived at all, write in from the address you used and give us the product name.
The link I saved has stopped working.
Your original download link stays valid and picks up new versions of the same product, so keep it. If it has gone stale, message us from the address the order was placed with and we will sort out access.
Can I get a refund?
All sales are final once your download link has been issued, and the refund policy sets out the exceptions we do review: a double charge, a link that never arrived and cannot be resent, or a resource that is provably broken on a supported framework version with no fix coming. Write in before you raise anything with your bank. A chargeback opened without contacting us first gets answered with the order record, and it costs you your downloads.
A resource will not start on my server.
Read the console from the top. The first error is the one that matters and the rest are usually its consequences, which is why scrolling to the bottom sends people chasing the wrong thing. Then confirm the resource’s dependencies are installed and started ahead of it: ox_lib, an inventory or a targeting resource loading late throws errors that look nothing like a load-order problem. The manifest guide and the error reference cover most of the rest. Still stuck? Send the exact line.
Will this work with my server?
Every product page names the frameworks its creator supports. The badges on the card come from the compatibility list the creator filled in, not from the product title, and creators write titles to be found. Where the two disagree, believe the badge. Want it checked? Name the product, then tell us your framework and version, your inventory and your targeting resource. The QBCore, ESX and Qbox shelves are already filtered.
My payment was declined, or I am not sure it went through.
Check your billing details and whatever your bank told you. Do not run the payment again on a guess: write in with the product name and the address you used, and we will tell you what reached us.
Send a message
What to send us
The messages we answer in one go all look the same. They name the product. They arrive from the address the order was placed with, and they quote the error instead of describing it.
Your order and your email
Write from the email address used at checkout. That single detail is what lets us find your order without a round trip, and it is the most common reason a reply takes an extra day.
Your server, in one line
Name your framework and its version, your inventory resource and your targeting resource. QBCore with ox_inventory behaves differently from QBCore with qb-inventory, and most compatibility questions are answered by that line alone.
The error, not a description of it
Paste the console output, starting at the first red line. A sentence on what you expected and what happened instead is worth as much as the trace itself. Screenshots of a console are harder to read than text, and we cannot search them.