Pushing 3rd party sales total via API in excess of LS-calculated total w/ tax

itristanjasonitristanjason Member Posts: 1
edited June 2020 in Apps & Integrations

We are completing another Lightspeed 3rd party platform integration from an external ecommerce platform and have a bit of a conundrum:

Due to rounding and potential global/regional tax calculation complexities (think USA Wayfair), it makes the most sense for us to send Lightspeed subtotals without, ourselves, calculating the tax.


Lightspeed needs to receive a cash value (assuming we're using "cash" method) of <total>=<item-value>+<tax-total>

| it won't accept a total less than its expected total; it will throw an error


| we don't know what that true total is because we're not calculating the tax, Lightspeed is.

So what we've discovered...

| is that Lightspeed API will accept a <total> from us via API as long as it is greater than Lightspeed's own <total> once it figures it out on its own.

| that could be a wee bit higher; or five times higher, doesn't make a difference, it appears to accept all values higher than its final tally it will eventually come up with.

| so then Lightspeed finalizes its own tax-in <total> and then appears to disregard the cash amount <total> random high number we fed into the API and sticks with its own "real" <total>

  1. Is this correct behaviour from Lightspeed's API?
  2. is there any unseen problem/failure we might create by submitting this semi-random high-value <total>??


shirt price 100 + 5% (for that region that LS eventually calculates) = $105

we have already fed LS API a <total> guess of $200 so that we are "clear" of Lightspeed's internal final <total>

Lightspeed appears to take/keep $105 from our cash payment via API and disregards the $95 overage entirely.

Is this correct LS behaviour?!



Sign In or Register to comment.