vend / developer-wiki Goto Github PK

You guys trigger multiple webhook events per single action.
for example

• product save triggers n + 1 events (n = number of variants)
• order create triggers product save and order create

Some suggestions:

• Don't trigger a product.update event when a sale has been made, It should be up to the developers to integrate all available webhooks to create a functioning system. Multiple events can cause race condition issues that are impossible to mitigate for. (Ive actually had to hard code sleep intervals in the vend integration so orders come before product updates and stock resolves correctly)
• Don't trigger product.update when consignments have been sent or received. Same issue as above

Currently we need to append to order notes with the App name so users know It was us that created the order / modified the product etc etc. Would be nice to have the App name instead of the user that Auth'd the App

You guys need to add security to your webhooks, have a look at how shopify does it:
https://help.shopify.com/api/tutorials/webhooks

You'll need to pass it as a param on the oAuth callback.

Not the highest priority for us, because we will be adding a param to the webhook URLs to prevent any sort of attack - however you guys should be aware that all your current integrations are easily hackable

Would be nice for ecommerce sites to be able to redeem gift cards via the API.

Expected Behavior

• Validate a coupon and receive the amount to discount
• Push coupon back to Vend with the order, which would then mark it as used.
• Optional, could allow purchasing of gift cards, but I think the basic redemption feature is what's firstly required.

Expected Behavior

A simple API to create/edit/remove a configurable button in the UI would allow many useful integrations to Vend. What could be configured:

• Label of the button
• Color
• URL to call
• (optional) where to locate the button, e.g. the customer area, the sale lines, etc

Clicking the button would open the URL in an overlaid iframe, and pass as a POST parameter the payload of the sale (customerId, sale lines). The iframe component is important because it allows using the Vend javascript API such as the 'add-product' method to directly modify the sale.

Context

In the context of a loyalty/CRM solution for Vend, we need to be able to read a current sale (customerId and sale lines), and be able to modify the line items. In the absence of this, we have needed to build a browser extension to reproduce this functionality. It's cumbersome for the retailers, breaks on DOM changes, and is a poor overall experience. This would allow us to ditch the browser extension. As soon as we would connect via OAuth, we'd call this API, and the button would magically appear in Vend.

Can you please provide a header on Webhooks that indicates that they came from a CSV import so we can prioritise them as low and use our clustering and merging methods to make the import more efficient

I'd like to add a 'Quick Add to Cart' that shows next to all products to create a quicker shopping experience as I'm building a eCommerce site for a groceries store based on Vend & Vend eCommerce

Requirement

• A mobile-friendly/ responsive UI/UX to add a product directly to cart, and return to the page end user is browsing, instead of going to the shopping cart
• Able to deal with product variants from within the Quick Add to Cart experience

Any information / reference for that would be appreciated. I am 1-week new to this platform and also new to Liquid.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

• Environment name and version (e.g. Chrome 39, node.js 5.4):
• Operating System and version (desktop or mobile):

Motivation

I want to be able to take a data dump and mimic customer environments for testing. This often requires populating similar products which requires populating similar taxes and outlets and such.

Requirement

It would be a good start to get a POST endpoint to create outlets so we can begin the journey to one day seamlessly copy a subset of customer account for testing in our vend subdomain before delivering solutions.

cc @ysg410 @szeber

A lot of modern APIs are moving away from timed interval throttling to leaky bucket which allows for a more consistent distributed load.

Check it out here!
https://en.wikipedia.org/wiki/Leaky_bucket

You can still achieve the same API limitations without freezing your API for 5 minutes!

If I have a product with 50 variants (we actually have customers with this many + more) It should only be 1 API call.