Marketing demanded IT add website feature that was already working
A marketing team member at a British retailer requested the addition of Apple Pay to the company's website, unaware that the feature was already operational. The IT team confirmed that Apple Pay was indeed functioning and generating revenue. The situation highlighted a disconnect between marketing and IT regarding awareness of existing features.
- ▪The marketing team believed Apple Pay was a new feature that needed to be added to the website.
- ▪Hamish, an IT team member, confirmed that Apple Pay was already available and operational.
- ▪The issue arose because the marketing team member was using an Android device, which did not display the Apple Pay option.
The Register publishes from United Kingdom and files mainly under tech. We currently carry 299 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | www.theregister.com - Articles |
| Canonical URL | https://www.theregister.com/software/2026/05/22/marketing-demanded-it-add-website-feature-that-was-already-working/5242367 |
| Publication time | Fri, 22 May 2026 08:31:00 +0200 |
| Retrieval time | 2026-05-22T07:07:00.807Z |
| Last seen | 2026-05-22T07:57:21.385Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Yen7Dzefv9ey |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); Software Marketing demanded IT add website feature that was already working Techie regrets not taking credit for getting it done with amazing speed Simon Sharwood Simon Sharwood APAC Editor Published fri 22 May 2026 // 07:31 UTC ON CALL Welcome to another edition of On Call, The Register's weekly reader-contributed column in which you share your stories of absurd tech support situations.This week, meet a reader we'll Regomize as "Hamish," who told us that a couple of years ago he worked…
Excerpt limited to ~120 words for fair-use compliance. The full article is at www.theregister.com - Articles.