The brewery's sellable products (casks, kegs, smallpack, multi-packs, stock items, services) with code, type, price and the drink(s) each contains. Obsolete products are left out unless asked for. Uses GET /products/.

One product in full: code, type, price, barcode, volumes, duty, the drinks and stock items it is made of, tags and custom fields. Uses GET /products/{id}/.

Current stock. Two sources: (1) stock items (ingredients, packaging, chemicals, guest beer, merchandise) currently in stock, per stock item and location, from GET /stock-received/ with is_empty=False (quantities in kg, litres or units depending on the item's tracking type); (2) finished products, from GET /products/ with include_fields=quantity_in_stock_in_format, a conditionally included field that Breww's API guide names but its spec does not define, so the value is passed through exactly as returned. The API has no location filter on stock received, so location_id is applied here after fetching.

Drink batches (brews) with drink, status (planned, in progress, complete), planned and actual dates, volumes and current vessel. Uses GET /drink-batches/.

One drink batch in full: drink, status, brew type, dates, planned and actual volumes, ABV, starting and final gravity, current vessel and fill, recipe version. Uses GET /drink-batches/{id}/.

Trade customers, leads and suppliers (Breww keeps them in one list) with last order date, predicted next order, ordering cadence, average order value and Breww's nightly churn and overdue probabilities. Good for 'who is overdue to reorder?' (next_expected_order_before today) and 'who have we lost?' (min_prob_churned). Contact details only with include_contact_details. Uses GET /customers-suppliers/.

One customer in full: type, sales person, price book, credit limit, payment terms, ordering cadence and predictions, trade store access, comments, number of contacts, and their most recent orders. Contacts (names, emails, phones), addresses, tax number and custom fields only with include_contact_details. Uses GET /customers-suppliers/{id}/ and GET /orders/?customer={id}&ordering=-issue_date.

Sales orders, which in Breww are also the invoices: number, customer, issue and due dates, order and payment status, value, total and amount due. Filter by customer, status, payment status, dates, amount due, number, PO number or source. Good for 'what is unpaid and overdue?' (payment_status unpaid/part_paid, due_before today). Uses GET /orders/.

One order/invoice in full: lines (product, quantity, dispatched, returned, unit price, discount, value, tax, total), adjustment lines (delivery, deposits), totals, statuses, delivery, notes. Billing and delivery addresses, the contact email and the invoice PDF and customer links only with include_contact_details; payment records are never returned. Uses GET /orders/{id}/.

Deliveries, collections, courier shipments and uplifts (Breww calls them fulfillments) with scheduled date, customer, order, dispatch and completion status, drop window and what is on board. The town is returned by default; the full address, phone number, coordinates and delivery-note links only with include_contact_details. Uses GET /fulfillments/.