Payment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.
Example result
Code review: Python order-import script for a small online shop
What the code does
- Reads
orders.csvfrom the shop export. - For each order line, finds the product by SKU in
stock.xlsxand subtracts the quantity. - Writes the updated stock back and logs totals to
import_log.txt.
The structure is clear and functions are well named. Most issues are about input that does not look the way the script expects.
Bugs and weak spots
| # | Line | Severity | Issue |
|---|---|---|---|
| 1 | 48 | High | The same CSV can be imported twice; there is no check for already processed order IDs. This is the most likely cause of negative stock. |
| 2 | 72 | High | int(row["qty"]) crashes on empty or "2.0" values from refunded orders. |
| 3 | 95 | Medium | SKU lookup is case-sensitive: "gt-101" and "GT-101" are treated as different products. |
| 4 | 130 | Medium | The file is opened without encoding="utf-8", so product names with accents break on Windows. |
| 5 | 201 | Low | Bare except: hides real errors and makes the log useless. |
Corrected fragments
Issue 1: skip orders already imported
processed = load_processed_ids("processed_orders.txt")
for row in reader:
if row["order_id"] in processed:
continue
# ... existing logic ...
processed.add(row["order_id"])
save_processed_ids("processed_orders.txt", processed)
Why: each order is applied once, even if you run the script on the same file again.
Issue 2: read quantity safely
raw = (row.get("qty") or "").strip()
try:
qty = int(float(raw))
except ValueError:
log.warning("Order %s: bad quantity %r, skipped", row["order_id"], raw)
continue
Why: refunded or partial lines are skipped with a clear note instead of stopping the whole import.
Issue 3: normalise SKUs
sku = row["sku"].strip().upper()
Apply the same .strip().upper() when building the stock dictionary.
Style and readability
process()is 90 lines long; split it intoread_orders,apply_to_stock,write_report.- Replace magic column numbers (
row[7]) with header names.
Please test each fix on a copy of your files: we read the code but did not run it.
Client: owner of a tea shop who wrote a 310-line Python script that imports orders from a CSV export into the stock spreadsheet Problem reported: "Sometimes stock goes negative, and the script crashes on some files."
The client and all details are made up.
About this service
Layout bugs usually come down to a few causes: a fixed width that overflows on phones, a flex or grid container set up the wrong way, a z-index that fails because of a stacking context, or media queries that fight each other. Paste your HTML and CSS with screenshots of how it looks and how it should look, and we explain why the layout breaks and give corrected CSS. We also note quick accessibility wins such as alt text, form labels and heading order.
What is included
- What you getA written review on the order page: why the layout breaks, corrected HTML and CSS fragments for desktop and mobile, and accessibility notes. Premium adds a plan for tidying the stylesheet into reusable classes.
- Layout fixesFlexbox, grid and overflow
- Responsive rulesMedia queries that do not clash
- Stacking and z-indexWhy elements hide behind others
- Semantic HTMLHeadings, landmarks, buttons
- Accessibility basicsAlt text, labels and contrast
How it works
- 1BriefYou paste the code and screenshots
- 2ReadingWe find the rules that break the layout
- 3ReviewYou get corrected CSS and notes
What we need from you
The HTML and CSS pasted as text, screenshots of the problem on desktop and phone, the browsers where it happens and how it should look.
We will ask you:
- Is it plain CSS or a framework?
- On which screen sizes and browsers does it break?
- How should the section look?
- Is the page built in a site builder or written by hand?
Compare packages
| Packages | BasicMarkup up to 100 lines$15 | StandardMarkup up to 400 lines$35 | PremiumUp to 1,000 lines with a stylesheet plan$69 |
|---|---|---|---|
| Deadline | 1 day | 2 days | 3 days |
| Revisions | 1 | 2 | 3 |
| Lines of code | up to 100 | up to 400 | up to 1,000 |
| Corrected fragments | Yes | Yes | Yes |
| Stylesheet clean-up plan | No | No | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Do you check it in real browsers?
No, we read the code and your screenshots. Check the corrected CSS in your browsers before publishing.
Can you fix a page made in Wix or Tilda?
Only the custom code you add there. The builder's own layout is controlled in its editor, not in code you can send.
Is this a full accessibility audit?
No. We note clear issues in the code you send; a full audit needs testing with screen readers on the live page.