Need help using the Syrve integration? In this article, find solutions to common errors and issues.
Error or issue | Solution |
Product sync fails with error: Updating the path 'calories' would create a conflict at 'calories'. | This happens when a product field is left blank in Syrve, which sends a null value instead of 0. Set a value of 0 (instead of leaving it blank) for any nutritional or numeric fields with no real value, then sync your products again. |
Orders get stuck in “Received” and never move to “Accepted”. | Syrve doesn't always send a failed status back, so a stuck order usually means a mandatory option in Syrve wasn't included on the item. Check the order in Syrve for missing mandatory modifiers and correct the product setup. |
Order fails with: “Payment of card payment type must have type=CardPayment or type=CardTipsPayment, but has type=CashPayment.” | The wrong payment type is mapped in your Syrve configuration (card payments are mapped to cash). Update the payment type mapping in Syrve so card payments use the correct card payment type. |
Menu items with different sizes appear as separate, oddly named products instead of one item with size options. | Syrve handles sizes separately from modifiers, so Deliverect receives each size as its own product. Convert your Syrve sizes into modifier groups so they sync correctly as a single item with options. |