rema-discovery

name	rema-discovery
description	Discovery workflow for the rema CLI. Browse current offers and bonus missions, check weekly sales campaigns, find stores, and view transaction history. Use when exploring what's available at REMA 1000.
compatibility	Requires rema binary installed and authenticated (see rema-shared skill).

rema-discovery

Workflow for discovering offers, campaigns, stores, and account information via the rema CLI.

Check Bonus Balance and Profile

Quick check (bonus balance + home store only):

rema customer minimal --json

Full profile:

rema customer get --json

Change home store:

rema customer update --home-store <workplace-id>

Browse Current Offers

rema offers list --json

Returns available offers, bonus missions, and non-activated price cuts. Use --fields to filter — the response can be large.

View Weekly Sales Campaigns (Superpriser)

Full campaign with product details:

rema campaigns list --type SP --json

Campaign metadata only (no product details):

rema campaigns list --type SP --no-offers --json

Campaign without feed data:

rema campaigns list --type SP --no-feed --json

Campaign type SP is "Superpriser" — the weekly flyer with discounted products.

Find Stores

Search by name, zipcode, or store number:

rema stores search "Grunerlokka" --json
rema stores search 7033 --json

Get store details by workplace ID:

rema stores get 1011141087892 --json

Get weekly opening hours by store number:

rema stores hours 3198 --json

Note the two different ID types:

• workplace-id (long numeric, e.g., 1011141087892) — used with stores get
• store-number (short numeric, e.g., 3198) — used with stores hours

Both are returned by stores search.

View Transaction History

List recent transactions (store, date, totals, payments):

rema transactions list --json

Returns headers including transactions[].id, storeName, purchaseDate, amount, bonusPoints, and transactionPayments[]. This is enough for most receipt-metadata queries.

Fetch line items (products purchased) for one transaction:

rema transactions get <transaction-id> --json

The get response contains:

• rows[] — each purchased line with productDescription, unitPrice, amount, pieces, volume/unit (EA or Kg), deposit, discount, and bonus earned. prodtxt3 is the GTIN when known.
• transactionPayments[] — payment breakdown (duplicated from list).
• bonusPointsTotal / bonusPointsTotalDecimal — bonus earned on this transaction.

Only call get when you need line items — list already has store/date/totals/payments.

View Product Images

rema articles image <gtin> --output product.webp
rema articles image <gtin> --no-webp --output product.png

Quality levels: 1 (thumbnail), 2 (higher, default).

Tips

• Start with rema customer minimal to confirm auth works and see your home store.
• offers list combines multiple offer types — filter with --fields to focus on what matters.
• Campaign responses are large. Use --no-offers if you only need the campaign dates and metadata, not individual product listings.
• Store search accepts zipcodes, store numbers, and name fragments — it's flexible.
• stores search returns both workplaceId and storeNumber — note which commands use which.