Create & edit beers & products via API

Ideas & feature requests
1

Good job getting the API out guys. Looks good.

Would be great to start to see APIs to create & edit things - especially beers, products & price books from our perspective.

3 Likes
API support to create/schedule batches and push per-batch adjustments
2

We help brewers with actionable insights to improve their data quality, and thereby reduce communication efforts towards wholesalers. Right now information lives scattered across too many administrations (breww, sharepoint pages, onedrive word template, etc). We want to send back the data that was enriched through our platform.

As a starter, having PATCH available for the Breww beers, products and container types will help breweries in not having to run an administration in two places.

The specific fields we want to patch (most relevant ones in bold) are:

  1. product
    1. gtin / barcode_number
    2. custom_fields
    3. name
    4. net_weight
    5. nominal_excise_duty_amount
    6. obsolete
    7. price
    8. tags
    9. weight
  2. container_type
    1. default_net_weight
    2. default_weight
    3. gross_capacity
    4. name
    5. non_returnable_cost_per
    6. stock_valuation_additional_cost_per_container
    7. taxable_capacity
  3. drinks
    1. alcohol_percentage
    2. degrees_plato
    3. ibu
    4. name
    5. style
    6. tags
    7. trade_store_description

Creation in our opinion should keep happening in Breww, as it involves quite some form logic that is different per type. The focus thereby could be to allow patching fields that do not impact complex (background) processing.

2 Likes
3

I’d like to add some weight to this request!!

We have our Product Master data created first in the core ERP / Finance system. That is typically where i would think core master data should continue to live and be managed for us. We therefore need the ability to specifically POST new finished products in to Breww via the Breww API. This would close the loop on a key bit of our integration scope, avoid manual rekeying of critical data and all the potential failed integration problems that mistakes can cause here.

@luke

1 Like
4

Thanks, Martin. Please make sure to vote for it, as that will add the weight you’re looking for (which isn’t done in the same way by a comment).

For more on how we manage feature requests or to see how to vote, please see 💡 Posting ideas & feature requests for Breww 💙

5

Hi Martin, curious to hear why Breww isn’t your initial data system for many of the fields above. The simple explanation is the fact that you’re using Breww; it adds value on top of your ERP / Finance system, and offers more specific functionalities that generic ERP isn’t focussed on providing. Likely it is a starting point of many of the primary or secondary business processes. Aren’t you missing out on almost the entire featureset within the lifecycle a product can have in Breww when you’re posting a finished product?

Having said that; I do agree that Breww having extensive read / write capabilities is a significant enabler to customize workflows to each brewer’s liking. In my opinion, having webhooks on CRUD actions is tightly related to that, so maybe we can reword / include this ticket together with it: Zapier integration

1 Like
6

Hey @rvanlaak - Breww is just a manufacturing system for us, ERP is responsible for all Sales and Financial Planning, we also have a lot of business processes tightly integrated to ERP which were in place before we implemented Breww. I’d also say we are a much larger than average brewery than the core Breww customer base, so our requirements are just more complex.

The API would be much more useful in different integration scenarios with wider support for all applicable CRUD operations across all endpoints, so agree with you there.

2 Likes
7

I think more put/patch/post options would be good across the API. So have a vote.

2 Likes