Need help using the Zelty integration? In this article, find solutions to common errors and issues.
Error or issue | Solution |
Invalid PLU: one or more items in the order has a PLU that doesn't belong to this location's POS. | Make sure the location is synced and the menu is published. If the menu uses products created for a different location, confirm all items are available in both locations. |
Invalid Delivery PLU / Invalid Service Charge PLU / Invalid TIP PLU. | Create matching delivery, service charge, or tip products in your POS back office, then sync and set them in your channel settings. |
X is a variant, but the order does not contain a variation sub item. | Check that the variant is built correctly with its variations, and make sure the variations aren't all snoozed. |
POS doesn't support internal products. | Check the order for the problem item — this is usually a meal deal with no sub-items. Make sure all variants and meal deal items are created correctly using POS items as sub-items. |
Reachable but takes too long to respond. | This points to a connectivity issue. Contact Zelty support to resolve the connection problem. |
Invalid API response. Status: 400. Error: String is too long: 10 chars max. | Zelty limits the order ID (display_id) field to a maximum of 10 characters. Contact our support team if this keeps happening. |
Invalid API response. Status: 400. Error: Transaction method not found. | The payment method isn't set in your Deliverect channel settings. Edit the channel settings and select the correct payment method option. |
Invalid API response. Status: 400. Error: Cannot find menu. | The item's PLU no longer exists in Zelty. Sync your products and publish your menu again. |
Invalid API response. Status: 403. Error: You've been blocked / Sorry, you cannot access this page. | Your API key has been removed or revoked. Create a new API key/token in your Zelty back office and provide it so it can be updated in your location settings. |
Invalid API response. Status: 403. Error: Authorization refused. | Your Zelty account authorization or token has changed. Confirm with Zelty support and provide a new token. |
No product sync data provided. | Check that your POS integration details are correct, and confirm you have active items configured in the POS with PLU values set. |
Location does not have any channelLinks. | A location needs at least one channel link to sync products. Once a Deliverect channel is created for the location, sync your products again. |
POS not reachable. | This indicates a connection issue between Deliverect and your POS back office. Check your on-site internet connection and try again. |
Too many POS requests error: rate limit reached. | Wait a few minutes before syncing again. Avoid running multiple syncs within a short time window. |
Invalid API response. Status: 404. Error: Resource not found. | This usually means the wrong catalog is being synced or an incorrect Auth Token is set. Contact our support team to verify your location settings. |
Order ID not showing on KDS or POS tickets. | Activate the option to display Partner IDs on your KDS. Contact Zelty support if you need help enabling this. |
Discount ID not showing in Deliverect. | In Zelty, the discount must be configured as an open value discount, created as an automatic promotion (not a manual code), and have a valid start date in the past. |
All orders show as “Deliverect” instead of the actual delivery channel name (e.g. Uber Eats, Just Eat). | This is a current limitation of the Zelty integration — order source is always shown as the partner name. You can edit your note template to display the channel name and order ID instead. |
Some products don't appear when syncing. | Check whether the item is tagged in Zelty as only available in the POS — tagged items are excluded from sync. |