Design review · 14 August 2026
Kattouf Jewellery
a new storefront.
Five pages are ready to look at, built with the real catalogue. Everything we need answered before building starts is below, grouped by who answers it.
For Kattouf to review
The design
These are working pages, not pictures. Open them on a phone and a computer, scroll, use the filters, click through. Every piece, price and photograph is taken from the current site.
Three decisions built into what you are looking at
An engagement ring is rarely bought on a screen without being seen. Rather than fight that, the site treats a booking as a success, not a lost sale.
“Made here, not sourced” runs through the site, because almost no competitor can say it. It is the strongest thing Kattouf owns and the current site mentions it in passing.
Where only one exists, the site says “only one available” instead of quietly limiting the quantity. It is honest, and it creates real urgency.
Affects cost and timing
What we found in the catalogue
| What | Detail | What it means |
|---|---|---|
| Products | 918 | A large catalogue. Filtering and search have to be built properly, which is included. |
| Discounts | ~40% | Almost every piece carries one. The site shows both prices — which works only while the discounts stay seasonal. |
| Specifications | Unstructured | Metal, carat and stone data sit in one block of text. We wrote software that reads it, and it now works on every product tested. |
| Placeholder records | ~29 | Around 3% of products are named 123-5, 2-1 and similar. These need real names before they move across. |
| Photographs | ~3,700 | About four per piece, around 1500 pixels. Fine for browsing, thin for the large views the design uses. |
Google currently sends customers to all 918 product pages, and that traffic is attached to the existing web addresses. When the site moves, every old address must redirect to its new one — otherwise the traffic disappears, and it is slow and expensive to win back.
We have already collected the full list of addresses, so this is work we know how to do. It is flagged because it must happen at launch, not afterwards.
Only Kattouf can answer · reply by number
Questions for you
Does the design direction have your approval, or what would you change?
Everything else waits on this.
The site launches in English only. Do you want Arabic and Hebrew later?
We build so they can be added without rebuilding — but translating 918 products is a separate cost.
Who will look after the website day to day, and are they comfortable with a computer?
We shape the admin screens around that person.
Which collections are still current — Fire & Ice, Inception, Kattouf Lily, Through Generations, Youthful Gems, 21 Modernity, Cameo, Crown Jewels?
Eight is a lot to feature well. Four done properly beats eight done thinly.
Will you rephotograph the lead pieces of each collection?
The single change that would most raise how the site feels.
Who will correct the ~29 placeholder product names, and by when?
Needs someone who knows the pieces. It cannot be guessed from the data.
How do appointments work today — who receives them, and is there a calendar?
The site pushes appointments hard. Requests arriving with nobody answering becomes a problem, not a feature.
Which countries do you ship to, who carries it, and who pays?
The current site advertises worldwide shipping. We need the real rules, including customs.
Is 30-day returns correct, and does it apply to sized or engraved pieces?
This is written on the pages you are reviewing. It must match what you will honour.
Does every piece come with a certificate, or only above a certain value?
Also currently stated on the product page.
“Make it personal” — should customers be able to request engraving and bespoke work online?
One of the strongest services, almost invisible on the current site.
Should customers create accounts and save favourites, or is guest checkout enough at launch?
Accounts help marketing later but add work now.
Please forward this section
Questions for your development partner
These decide how the site connects to Priority, and how it is kept safe once it is live.
How is Priority reached — REST API, OData, middleware, or a database view?
Decides whether the site syncs directly or needs a service in between.
Is the catalogue code on the website (e.g. 0652.WR.B_G14KW) the same identifier used in Priority?Blocks build
This is the link between the two systems. If it differs we need the real key and a mapping table.
Do prices and discounts come from Priority, or are they maintained separately for the web?
Both systems must not be able to change a price, or they will disagree.
Is stock accurate at individual item level?
For one-of-a-kind pieces, selling the same ring twice is a serious failure.
When an online checkout begins, can the piece be reserved in Priority and released if payment fails?Blocks build
Without this a piece can sell at the counter and online in the same minute. With unique pieces that is a certainty over time.
Are the photographs in Priority the ones to publish, or inventory reference shots?
If they differ, the site needs its own image library alongside the feed.
What shape should an order take in Priority — header, lines, customer, tax, shipping?
We need the target structure before designing checkout.
Is there a Priority test environment we can push to?Blocks build
Without one, the first real order is also the first test.
Which Priority–WooCommerce connector will you use, and have you deployed it before?
Several exist, including one on Priority's own marketplace. Experience beats feature lists.
Who hosts the site, and does it include staging, caching and daily off-server backups?
Inexpensive shared hosting will not carry 918 products with photographs.
Who owns security updates, monitoring and backup restoration after launch, and under what agreement?Blocks build
The most important question here. A shop taking real payments cannot be left unattended.
Please forward this section
Questions for PayPlus
Which integration is provisioned — hosted payment page, iframe, or direct API?
We are planning on the hosted page, so card details never touch the Kattouf server.
Are server-to-server callbacks available to confirm payment, and how is authenticity verified?
Payment must be confirmed by your servers, not the customer's browser.
Is there a test environment with test cards?
Needed before launch and for every future checkout change.
Which payment methods are enabled — local cards, Apple Pay, Google Pay, instalments?
Instalments matter at jewellery prices and change checkout design.
How are refunds and partial refunds issued — dashboard, API, or both?
Returns are certain. The path must exist before launch.
Is multi-currency supported, and does settlement stay in shekels?
The site advertises worldwide shipping, so overseas buyers are expected.
Materials, not answers
What we need from you
Received and redrawn as artwork that stays sharp at any size, on light and dark backgrounds.
See question 5. If you are rephotographing, the sooner the better.
See question 6.
Shipping, returns, privacy, terms. We can draft them for your approval.
The 1907 text on these pages is our draft. It should be checked by the family — names, dates and details matter.
What happens next
- You review the five pages and answer questions 1–12.
- You forward the development partner and PayPlus sections.
- We meet to go through the answers and agree what is in the first release and what waits.
- Building begins — the design becomes a real WooCommerce site, and the technical team connects Priority and PayPlus alongside.
Questions 14, 17, 20 and 23 are the ones that would hold everything up if they arrive late. If you forward only one thing today, make it the development partner section.