Pictures, wishlists & lookbooks

In a considered purchase the sale is often made by a photograph sent at the right moment: "the green dial came in, and I thought of you". Stitchwork keeps a picture of every piece, what each client has their eye on, and lets you send one client a short personal edit that they answer from their phone.

Product pictures

Every product, and every variant, can have one picture. It is an address, not an upload: paste the link to a photo that is already on your website or Shopify's CDN. A variant's own picture wins over its product's, so the green dial shows the green dial.

Where they show: the catalogue, the product page, the quote builder, your quotes and the client's quote page, the client's Orders tab, wishlists and lookbooks.
Importing: an image_url column (also read as image or image_src), and variant_image_url for a variant's own. A Shopify product export's Image Src and Variant Image columns are read as they are, and a connected Shopify store brings its pictures in by itself.
The rules: the address must start https://, may not contain a username or password, and is at most 2,048 characters. Pages sent to clients are secure, and a browser blocks a plain-http picture on them.
A missing or broken picture shows a quiet placeholder, never a broken-image icon.

The wishlist

What a client has their eye on lives on their record, under Wishlist: the piece, today's price, a note ("loves the green dial — birthday in March"), and who added it and when. Add a piece from the client's record by searching the catalogue, or press Save for a client on any product page and choose them. A piece the client loves in a lookbook is added for them.

Anyone on the team who can see the client can see and change their wishlist. Its notes are the team's and are never shown to the client.

Lookbooks

A lookbook is a personal edit for one client, sent as a link: a title, a few lines from the person who made it, and the pieces, each with a note. Start one from the client's record with New lookbook; the pieces on their wishlist go in first.

Build it. Add pieces from the catalogue, put them in order, write a line for each, and choose whether prices show. Preview shows the page exactly as the client will see it.
Send it. Send to Anna opens the composer on her record with a first draft in your words and the link in it: an email, or a text when she has only a phone number. You read it, change it, and press Send (see Messaging). Copy link works too, for WhatsApp from your own phone.
She answers. The page is made for a phone and signed with your first name. Under each piece she presses Love it, Maybe or Not for me, and can change her mind.
You hear. You are emailed the first time she opens it and whenever she newly loves something. Each answer shows in the editor beside the piece, loved pieces join her wishlist, and all of it is on her Activity tab.

Question	Answer
Who can open the link?	Whoever has it: 32 random characters, nothing to sign in to. A lookbook still in draft is not shown to anybody outside the team.
Do my own visits count as opens?	No. A signed-in member of the workspace previewing it is not the client opening it.
What does the client see?	The title, your lines, each piece's picture, name, price (if shown) and note, and the shop's address. Never the wishlist notes, staff surnames or anything else on the record.
Who can delete one?	Whoever made it, or an owner or admin. Deleting it stops the link working.
Is it in a client's data export?	Yes: every lookbook with its pieces and answers, and the wishlist.

API

The screens run on these endpoints, which take a signed-in session and return the usual {"version": "v1", "data": …} envelope.

Endpoint	What it does
`GET /api/v1/customers/{id}/wishlist`	The client's wishlist.
`POST /api/v1/customers/{id}/wishlist`	Add a piece: `product_id`, and optionally `variant_id` and `note`.
`DELETE /api/v1/customers/{id}/wishlist/{itemId}`	Take it off.
`GET` / `POST /api/v1/customers/{id}/lookbooks`	The client's lookbooks; start one (`title`, `intro`).
`GET` / `PATCH` / `DELETE /api/v1/lookbooks/{id}`	Read, change (title, intro, `show_prices`) or delete one.
`POST /api/v1/lookbooks/{id}/share`	Mark it sent, and get the draft message and link for the composer.
`POST /api/v1/lookbooks/{id}/items`	Add a piece; `PATCH` or `DELETE …/items/{itemId}` to change its note or remove it, and `POST …/items/{itemId}/move` to reorder.