Your app is printing the orders? What is the print trigger?
Thanks for your reply. As soon as new order comes from our mobile phone apps then our printing app which we have installed in clover register send the printing request
I am asking for details on what the print trigger is, otherwise I have to make assumptions. Does your architecture have its own messaging system? Or does your app rely on an order create listener on the device? What exactly does your app do to determine there is an order that needs to be printed? All orders will sync to all Clover devices so this seems to be expected behavior.
To be clear, is the issue that on a single device printing results in 2 receipts, or that you are multiple devices are each printing one receipt?
We have two clover devices and each printing once.
I see two options:
1) Jeff gave me this idea. Basically, you can have a configuration option in your app where you allow the merchant to select what printer they want to use for online orders (the merchant endpoint allows you to expand printers). Then your app can check which printer was configured and only print if a match is found.
2) My original idea, implement some short of messaging service that only delivers the print request to a single device.
Keep in mind, querying for orders as you are doing now may eventually lead to rate-limits so that is something you need to change as well.
Closing this post. The developer's application needs to be intelligent enough to print to a specific printer. This can be accomplished via configuration/code in the 3rd party app (allow merchants to select which printer orders should be printed on).
2 People are following this question.