Cost the catalogue update you can actually operate
“Connect our catalogue to the supplier” can describe anything from a daily file import to a supported exchange of changes in both directions. An estimate that assumes the most convenient interface may omit the work your staff will perform every day.
A useful cost review begins by inspecting the available capability, then assigning the preparation, checking and exception work that remains. The decision is not just how much development to commission. It is whether the organisation can operate the resulting arrangement honestly.
Establish the actual source capability
In this fictional trade-catalogue project, the supplier account permits a nightly downloadable export of approved product descriptions and pack references. The inspected arrangement provides no supported write interface and no on-demand live feed. Urgent corrections must be made in the supplier's own portal by an authorised operator.
The buyer-facing catalogue needs those descriptions for enquiries. It does not promise live stock or immediate price acceptance. That existing scope makes a supervised daily update a plausible option; the same arrangement would not satisfy a requirement to reserve current stock in real time.
The initial request called for “live two-way sync”. The team removes that phrase from the estimate because the available account does not support it. This is a project-specific observation, not a statement about all suppliers or products.
Follow one update through the operating day
Export EX-24 contains 120 approved product records. The catalogue operator downloads the authorised file, records its identity and prepares a candidate import. The importer checks the declared format, required references and relationships before publishing anything.
One record, P-86, has a pack reference that the catalogue does not recognise. The operator asks the supplier's responsible contact to clarify it. The agreed first release holds the candidate update until that exception is resolved; it does not silently drop the row or publish a guessed pack.
The corrected source export EX-25 is a separate file. Its complete import passes the checks, and the operator compares changed descriptions and pack meanings before approval. The public catalogue then shows its approved update date. It still describes an enquiry service rather than live availability.
Put recurring work into the comparison
The project compares three scopes:
| Option | Development obligation | Continuing responsibility | Fit for the inspected requirement |
|---|---|---|---|
| Claim live two-way sync | Depends on an unavailable supported interface | Undefined failure and correction handling | Cannot be responsibly estimated as available |
| Supervised nightly import | Candidate validation, review, publication and traceable source identity | Download, resolve exceptions, approve updates | Selected for the enquiry catalogue |
| Manual editing of every product | Editing workflow and source-reference fields | Re-enter and review each change | Possible, but duplicates more of the supplied file work |
The owner obtains the actual provider charges and estimates staff effort from a representative cycle before comparing the recurring cost. The proposal separately identifies development, hosting, approved source access, operator time, exception investigation and support coverage.
The supervised option is selected because it uses an available source and leaves a reviewable publication decision. It does not remove the need for a catalogue owner. A failed or missing export means the previous approved version remains visible with its actual date, while the operator follows the agreed escalation path.
Include the urgent exception
During the rehearsal, P-42 needs an urgent source correction after the nightly file has been prepared. The authorised operator changes it through the supplier's portal. That action does not instantly update the public catalogue. The owner uses the agreed temporary notice or withdraws the affected enquiry item until the next approved import, according to the site's actual publishing capability.
For this fixture, the owner withdraws only P-42 from new enquiries, retains existing enquiry history and records the reason. After the corrected export is reviewed, P-42 returns with the approved description. An unrelated P-43 remains available throughout. This exception has its own operating cost and acceptance check; it should not be hidden inside a promise of automation.
Check the proposed routine before committing
The intended operator performs the complete EX-24-to-EX-25 review with sample data. They can identify the rejected pack, locate the source correction, approve the candidate and explain the displayed update date. A missing file does not clear the catalogue. A mismatched source identity does not replace the approved set. The urgent withdrawal affects the intended item only.
If nobody can own those tasks, the selected scope is not ready simply because the importer works. The organisation can adjust staffing, reduce the catalogue or choose another supported arrangement before committing to the build.
Bring the actual export and its permitted use to the scope discussion. The trade catalogue service can then be estimated around a complete operating cycle rather than an interface that has not been demonstrated.