Written by DROPS.ST.
Give the application step to a named person whose actual access the owner accepts. Separate that step from preparing the file, approving its business changes and checking the result. One person may hold several responsibilities, but each decision should remain explicit.
DROPS gives bulk catalogue work a meaningful destination: products, prices, units, images and stock in one shop catalogue, shared by the website and connected Telegram shopping. That makes the scope of a proposed batch worth defining carefully before it is applied.
A checked file is not permission to change the shop
State the intended result, such as description changes with prices and stock unchanged. File columns should not decide business scope.
Confirm create/update/replace behavior, excluded fields and empty-cell effects in the actual process.
Name four responsibilities
Use this owner-managed process; it does not assume four software roles.
| Responsibility | Named person's job | Handoff condition |
|---|---|---|
| Prepare | Build the file and explain its source, fields and intended values | Identified file and checked sample ready |
| Approve | Accept the business changes and their limits | Scope and exceptions explicitly agreed |
| Apply | Use the supported process with authorized access | Approved file, destination and timing confirmed |
| Reconcile | Compare the result with the approved intent | Differences resolved or handed to a named owner |
One person may approve and apply; keep each decision and reconciliation explicit.
Examine the access behind the application step
The principle of least privilege is to allocate only the access needed for a person's work. OWASP recommends matching permissions deliberately to the responsibility. OWASP Authorization Cheat Sheet.
DROPS catalogue-edit access includes customer-account edits and wallet adjustments. Settings require an administrator. Confirm the actual importer permission separately.
Demonstrate the import process and full access scope. If broader than the preparer's job, keep application with the authorized operator.
Use the manager permissions checklist to examine that wider access. Approval to run one batch should not quietly become continuing authority over unrelated records.
Record a batch authorization that can be checked
Identify the exact file version, destination shop and affected items. Record the intended fields, expected create or update behavior and deliberate exclusions.
Name the approver, operator and reconciliation owner. Define when changed prices or stock make the file outdated.
Preserve affected pre-change values through the supported workflow. Plan corrections that retain unrelated later activity.
Inspect any supported preview. Otherwise demonstrate behavior safely; do not assume atomic application, history or automatic rollback.
Reconcile the intended changes, including what should stay unchanged
Compare the applied changes with approved scope, checking references, fields, images and reported failures.
Also inspect fields that were supposed to remain unchanged. A description batch that silently changes units or prices has not met its acceptance condition.
Matching row counts can conceal missing and duplicate items. Assign unresolved differences to an owner.
After an unclear result, inspect affected records before retrying; matching behavior determines the effect of another attempt.
Hypothetical example: descriptions only
A shop asks for a batch correction to fictional product descriptions. The preparer exports a file that also contains price and stock columns.
The approver notices that the file's scope is wider than the requested change. They ask which fields the supported process will apply and what will happen to excluded or blank values.
The file and mapping are corrected before authorization. The applying person uses the agreed version, while the reconciliation owner checks both the changed descriptions and the prices and stock that should remain unchanged.
Keep catalogue batches distinct from a full migration
Use migration rehearsal guide for a full platform move. Keep ordinary batch records proportionate to their actual effect.
Put bulk work into a shop the owner controls
DROPS is a strong fit for owners who want catalogue work to feed one shared website and connected Telegram shop. The practical value is a coherent destination for approved products, prices, images and stock, with responsibilities named around the work.
See DROPS and explore demo shops. Bring one proposed batch to the discussion. Establish its supported application route, complete access scope and acceptance checks before deciding who should apply it.