What to write on the first screen of an Alibaba.com detail page: this SKU’s specs and photo, do not stack a factory gate

Friday 10:20, a Turin machine shop asked on-site for sintered bronze bushing 20×14×20mm, then added I opened your detail page, first screen is a factory gate and a manager speech, I need OD, ID, length and tolerance on this size. Sales wrote our factory is strong, please see the workshop photos, we will rebuild the detail next week. Ten minutes later ops opened a “detail upgrade” folder and started lining up a gate, a workshop panorama, an honour wall, and a fifty-page catalogue long image. Buyer WhatsApp: I still cannot see 20×14×20 on the first screen.

Hong Kong shops have this meeting in the week the main image just swapped and the detail still runs last year’s plant film. Sales likes a gate to hold specs. Design likes the detail as a brochure. Ops treats page-count as complete. Turin walked in from the front and asked whether the first screen holds this bushing’s numbers. Twelve gate shots do not fill that sentence. Corpable Marketing Limited is a Hong Kong Alibaba.com official channel partner. An advisor can sit with you on the first screen. The advisor cannot write it, and cannot promise an inquiry after it is written.

Listing still one does not identify the goods: first still identifies the SKU. Already in the shop, asking about banner and tile one: which storefront block. RFQ hall first screen before submit: RFQ first screen. Which of twenty tiles to fill: which showcases. Turin did not ask for a main image, a storefront, an RFQ, or a tile. They asked why the top slice of this product detail does not face 20×14×20.

Turin opens the detail. The first screen is a gate group shot

Someone who can enter My Alibaba opens Product management and the detail editor on this 20×14×20mm sintered bronze bushing. Sales saying “our detail is very long” is not enough. A sub-account that only sees inquiries and cannot open edit: switch to one that can. Then open a logged-out window and look at the front first screen. First screen a gate, a manager speech, a full-series table, or a neighbour 25×20×25: write “first screen does not face this SKU.” How complete screen-four specs are does not enter this week’s change.

Turin’s original writes first screen and OD ID length tolerance. It does not write factory ugly. It does not write brochure too short. Sales forwarded it into the design group as “they think the detail is not grand enough.” Design will schedule a plant film. The store lead made them paste the original back. Pasted, it was clear: they hated that the first screen has no numbers for this bushing. A sharp gate still fills no 20×14×20. The same afternoon a German thread asked for 16×10×16 and a Spanish thread asked for a flanged bush. Three inquiries, three first screens, three mark pages, each reply on its own thread. One “detail upgrade” and all three will treat you as selling a gate.

On the phone app, the detail is often cut in half by the category bar and the inquiry button. The half still holds the gate. Specs have been pushed to a swipe. Desktop preview shows a full screen. Phone treats as phone. Turin buyers use phones. The cut slice this week lifts specs up. It does not add a brighter gate. A browser translate bar sometimes turns factory overview into “factory live shot.” Live shot will be heard as size already written. Open a window with no plugin.

Inquiries still arriving does not mean the first screen already faces this SKU. Someone sees an inquiry and replies buyers still come so the detail is fine. Turin will staff next week’s assembly on that sentence. Inquiries walk messages. First screen walks detail preview. Non-zero dwell on data tools also does not prove tolerance is readable. You can have dwell without this SKU, and this SKU without a question. Promising detail is fine from dwell is adding specs onto shop data.

20×14×20 is this ticket. The neighbour 25×20×25 is not. Someone opens a neighbour account, sees a first-screen spec table, and replies to Turin from it. Wrong shop. Ask which storefront entity before you speak. Oil content was not locked. I need sintered bronze bushing 20×14×20mm, then a follow-up adds 18% oil, locks a process on top of the first screen. Oil written into the title and the welcome line still writes 12%: you still face the first screen. Two characters will not talk a gate into a bushing.

How-to-sell writes reply soon. Reply soon is the sentence that faces the original on the first screen, not a faster “factory strength next week.” A response-lesson green only proves someone hit send. The sender may be the auto-welcome, and the welcome has no 20×14×20. Green does not fill the first screen. Friday afternoon ops left the detail editor open, ready to stitch twelve gate shots, and said “specs up tomorrow.” The store lead put the logged-out first screen on the second monitor. The second monitor was still a gate group shot. A gate does not cover that sentence.

Sales opens this detail in a logged-out window and grabs a phone frame and a desktop frame. Desktop faintly shows a size table, phone is blocked by a “source factory” float: treat the phone as empty. The blocked slice comes down this week. Do not beautify the gate first. File the frames in this ticket clip. No old frame and next week nobody knows it was a gate. Do not send a preview link to the buyer. Preview is not the front. They open a 404 and treat the shop as empty.

Sales marked the thread handled. The original is still there. First screen is still a gate. Handled does not fill specs. The store lead audits the handled list. Anything this week with bushing or 20×14×20 must point at what the first screen is now. Cannot point: send it back to open. An RFQ-hall quote on 20×14×20 walks the RFQ page. Do not fuse it with this detail.

Put 20×14×20 size, tolerance, and this SKU’s photo at the top

The first screen can read four things: OD 20mm, ID 14mm, length 20mm, and which tolerance grade is written. Four things in short sentences or one this-SKU table. Not a fifty-row full series. 20×14×20 buried on row 18 of a full series, Turin stops three seconds on the first screen and cannot find it. A this-SKU table can be one row. One row facing the original is cleaner than eighteen.

This SKU’s photo is this bushing, not a shop rack. Fifty mixed pieces on a rack do not read as 20×14×20. If you have a caliper, rest it on the OD, numbers to camera. If you do not, set the bushing on paper printed with a millimetre grid. Shoot the paper this week. Do not recycle last year’s catalogue “indicative 20×14×20.” Indicative is not this piece. Photo and table face the same piece. Do not write 20 on the table and show 25 in the photo.

If the attribute column already holds OD, ID and length, the column and the first-screen long image are two layers. The column sits on the right. On a phone it often needs another tap. Turin’s first screen is the slice you see on open, no scroll, no attribute tap. Column filled, long-image first screen a gate: they still treat it as not written. The posting lesson writes attributes as to-be-filled. A filled column is not a first screen that already faces this SKU.

If still one just became a white-background bushing this week, still one is the card. Detail is after the click. Both cells are needed. The main-image page stops on still one. This page stops on the first screen after the click. Still one facing, first screen still a gate: the person who clicked still cannot read a number. Membership wired to ALIBABA.COM HONG KONG LIMITED buys membership and showcase quota. It does not buy the first screen turning into 20×14×20, and it does not buy official dwell seconds. On the Hong Kong channel, Export Tong is about HKD 39,000 and Verified about HKD 108,000. That is the year, not a detail-completeness rate. An advisor does not read those two numbers as “paid, so the detail will face.” Pricing sits at Membership pricing. It writes packages by region. It does not audit this bushing’s first screen.

The original writes sintered bronze. A follow-up that adds we also do brass and iron locks two extra grades on top of the first screen. The two grades can sit in a later series. The first screen keeps sintered bronze. Three grades side by side and Turin will order the cheapest iron while the floor runs bronze. Two materials are worse than a gate. False specs are worse than empty. Empty and they still ask. False specs and they staff assembly on the wrong material.

Tolerance was not locked. The original wants tolerance. Do not volunteer h7 or F7 on the page. The follow-up asks which grade they want. Volunteer it and the floor cannot open that grade, and Turin receives to the page. Tolerance on inquiry on the page is fine. A grade the floor cannot hold is not. An advisor does not invent “Europe defaults to h7.” How-to-sell has no such line.

If a tier price already sits under the title, price is not first-screen specs. Price can face one this-SKU row. Do not stack eighteen sizes of price on the first screen and squeeze size off. How price splits sits on the freight page. Price can stay. Size cannot be squeezed off by price. Squeezed off, Turin sees a price and not 20×14×20, asks on price, and orders the wrong size.

If the floor this week can only shoot a gate, not this SKU, the first screen uses the sample-room 20×14×20 that is actually on the shelf. Sample and production differ by 0.05mm on ID: write the difference in the follow-up. Do not write it into the first screen as if there is no difference. Written into the first screen, Turin receives to the photo and production will not face the photo. Sample-room light too yellow: change to a white lamp and shoot again. Do not beauty-filter sintered bronze into brass. Brass is another grade.

Gate, full-series table, and manager speech scroll below

The gate can stay. It stays below specs and photo. No gate on the first screen, a gate on screen three, and Turin scrolls when they want the plant. Gate on top and specs scroll away. Ops says “European buyers look at the plant first.” Turin’s original on this thread writes size first. The original governs. Another thread that asks for the plant first walks factory video or storefront. Do not fuse it with this one into “everything starts with a gate.”

A fifty-row full series holds 20×14×20 and also a 30×25×30 you already stopped. A stopped row on the first screen and Turin will inquire the stopped size. Inquiry in, the floor says none, the thread splits. Put the series later. The front keeps this SKU. The later table marks which are stock and which need a tool. How a mould deposit is written sits on the mould page. This first screen does not show a “free tooling” button that covers size.

Manager speech, founding story, twenty years of export — three blocks are cousins of the profile. How profile fields fill sits on profile fills licence and plant. Do not embed two screens of history on the detail first screen. History hot, size cold. Turin opens the detail on a phone, the speech auto-expands and covers the table: treat the table as empty. That slice folds up this week.

If showcase tile one is also this bushing, the tile image and the detail first screen are two cells. How to pick tiles sits on the showcase page. This page does not stop on twenty tiles. It stops on this detail’s first screen. Tile swapped, first screen still a gate: they click in and still see a gate. A storefront banner that is also a gate is the shop, not this SKU. Do not fuse shop and SKU into one reskin.

The welcome line hangs a fifty-page catalogue, page 22 has this bushing’s size. A catalogue sent to someone still asking about first screen will be read as blocking specs with a book. The catalogue can stay in the sample room. The follow-up does not write see page 22. Page 22 is not the first screen. A forwarder quotes a container from the catalogue, the sailing date walks into rebuild next week, and booking and specs weld into one sentence. A booking page does not audit the first screen.

Night shift writes “the detail is very long so conversion is fine” onto the roster. Cross that sentence out. Long only proves a page count. Turin asked about the first screen. The roster writes first screen still a gate, this-SKU specs not lifted. The floor already staged 20×14×20 stock on “new detail next week.” Staging is inward. Outward, the first screen can still be a gate. Stock staged and night shift will say already reserved. Already reserved does not fill specs.

A size table on WhatsApp is fine. After you send it, write it back on the same on-site thread and swap the detail first screen. Locked 20×14×20 on WhatsApp, first screen still a gate on-site: they hold two pages. Two pages and receiving will ask which one governs. The sample room still holds a 25×20×25 old piece. People at the rack can argue 25. Do not write 25 into the follow-up as if it already became 20.

A new mailbox asks same bushing, still the gate? That is another thread. Copy first-screen original back onto the old thread. Do not retell factory strong in the new mailbox. The new thread has no old state. They still hold sales’ daytime see-the-plant sentence. An advisor WeChat that says “I will speak to the platform for weight” is not a page. It does not fill the first screen. Write on this thread: there is no official dwell second in chat.

The posting lesson writes attribute fields. It does not write stacking a gate as an inquiry

Open How to post products and read the original. Sales repeating “official says longer detail is better” is not a reading. The lesson writes attributes and description as part of posting, and information score 0 to 5. It proves fields should be filled. It does not prove Turin’s first screen already faces this SKU, and it does not write twelve gate shots as must-inquire. Score green, first screen can still be a gate.

How-to-sell writes posting as one open-store step. Steps have an order. An inquiry does not. Services at Seller services lists tools. A green tool entry does not mean the first screen is a bushing. The showcase tool writes tiles as replaceable. It does not audit whether this detail’s first screen is 20×14×20. The company-profile lesson at How to set up your company profile asks you to fill the fields. Filled is profile, not a detail first screen. The profile can be full and the first screen can still be a gate.

If the group only holds rumours — “over twenty screens must convert,” “gate on top and conversion doubles” — treat it as nobody opened an official page. Outside posts that write “bounce 40% is a pass” or “change the first screen and inquiries arrive in three days” are not words on your page. Do not write them to Turin. Do not write them into the GM’s weekly. An advisor does not invent bounce rate, dwell seconds, or inquiry counts. Impressions without clicks walks a funnel. A funnel does not fill “first screen is a gate.”

Review not passed sits on the product-review page. Review passed, first screen a gate: passed only proves the fields can go out. It does not prove 20×14×20 is readable. If the review note writes description incomplete, fill this SKU’s specs against the note. Do not borrow the note to line up twelve gate shots. The note did not write a gate. Account restricted sits on the restriction page. Here detail edit opens. Empty treats as not facing this SKU, not as banned. Listing removed sits on the takedown page. The shop is still asking about the first screen. There is nothing to take down.

Corpable on the page only checks whether you copied the posting-lesson original or a twenty-screen rumour from the group. Copied someone else’s bounce 40%: cross it out. An advisor will not read the posting lesson as “official says you must stack a gate first.” If Rule Centre currently posts something on product information, copy the title and keep it. A notice is not this shop’s first screen. partner.alibaba.com can confirm Corpable is an authorised channel. Directory green, first screen can still be a gate. Authorised is not a detail desk, and not a consulting invoice that covers conversion.

The main-image page stops on card still one. Turin already clicked in. That page does not audit this bushing stuck on a detail first screen, and it does not write factory strong as a step. The storefront page walks the shop’s three blocks. The shop can face and the SKU detail can still be wrong. The RFQ page walks the hall before submit. Fields before submit do not fill a detail already open. No-exposure walks three cells. They already opened the detail. Those three cells are not this week’s steps. Which open-store page you are stuck on sits on the open-store flow. Live is not a first screen that faces this SKU.

The advisor opens the top slice of product preview

The advisor sits. Design holds a twelve-gate schedule. Ops holds an information-score screenshot. Sales holds Turin’s English. Three sheets on the desk, none of them writes “is the first screen 20×14×20.” Design asks which day the gate set finishes. Ops asks whether the score can hit 5. Sales asks whether next week can reply already new. Nobody has read the top slice of product preview against the inquiry original. Twenty minutes of argument, then they open it: first screen is still a gate group shot. A size table does exist, buried on screen four. They saw a gate. They did not scroll to screen four. Hong Kong shops have this meeting almost every listing week.

When you face the page, write only the words on it. Product preview: what the first screen is, which screen holds specs, whether this SKU’s photo is there. Inquiry original: first screen, OD ID length tolerance. Logged-out phone: what you see on open with no swipe. Outside those three rows — “you can more or less tell,” “xiaoer said they will weight it” — do not write them to Turin. More or less is not a page. Xiaoer said is not a page. What the page shows, you reply. The words change: write them back on this thread. Old words stay — Turin is still staffing assembly on the old gate.

Someone will add Accio, top-of-search, or a CRM into the “detail plan.” Those are separate products. Some shops never bought them. Week one has none of those receipts. Talking packages is advertising a service that is not on the desk. Growth numbers on intro case studies do not become your shop’s result. The factory in the case is not this Ningbo powder-metal plant, and not this Turin machine shop.

The powder-metal plant’s habit is shoot the plant first, then write specs. A gate on the detail looks like strength. Turin’s ticket runs the other way: they want this bushing’s numbers before they write 20×14×20 into assembly. Habit reversed, sales still replies factory strong, and the thread splits. The gate can keep being prepared. Take the strength sentence off the follow-up first. Preparing a gate and telling them the detail is already being rebuilt are two sentences. The first is fine. The second is not sayable while the first screen is still a gate.

On the buyer side, search shows the first screen after the click, not your group schedule. An advisor sometimes has ops open this bushing logged out. First screen a gate: stop arguing “the back-end screen four should have a table.” Should see and did see differ by that top slice. Phone and desktop first screens disagree: write back which end shows what. Both a gate: treat as not facing this SKU. Do not fuse it into the whole shop banned.

This Ningbo powder-metal plant’s document habit is PI, contract, and Trade Assurance order facing on spec. First screen still a gate and the three have nothing to face. Someone already wrote 20×14×20 sintered bronze on the PI and a new HKD account on the payee, and has not opened detail preview. Spec written right, first screen missing, Turin still does not know if this is the piece. Papers can be prepared. Outward first screen cannot run plant film. Preparation is a table in the plant. First screen is a slot on an assembly line. A messy table can be tidied. A wrong slot waits a month.

Corpable does not collect. The advisor does not touch your master password. The year still goes to ALIBABA.COM HONG KONG LIMITED from the company’s account. Sitting beside you on the first screen is fine. The person who saves must be someone with product rights in the shop. After the swap, grab a frame: first-screen original, who clicked, when. File it on Turin’s thread and on the ops WeChat. No frame and night shift will say the gate “should already have been swapped.” Should is not a page.

If P4P is already buying this bushing, the campaign is bound to a gate detail. Swapping the first screen is not a reason to raise budget. The word is live, the screen changed. People who click in see numbers, then you talk about leaving it on. Which words to buy in week one sits on the P4P first-week page. Words not set yet, the first screen can already swap. Account paused sits on the ads-paused page. Pause is another ticket. It does not fill “first screen is a gate.”

Reply to Turin only that this SKU’s specs are now on the first screen

The person who may speak has opened product preview and seen first-screen original. A sales inquiry sub-account that has no such page does not say I already changed the detail in the group. Before speaking they can at least repeat whether the first screen is a gate or 20×14×20. Cannot repeat: say the master account is still facing detail preview. Do not report “factory strength.” Do not add a “detail upgrade progress” column to the roster. The posting lesson and how-to-sell give no upgrade day. Add the column and night shift will fill next week.

The sentence back to Turin is as short as it can be. First screen still a gate: first screen is still the factory gate, we are moving OD 20 ID 14 length 20 and the part photo to the top. First screen already this SKU’s specs and photo: first screen now shows 20×14×20 and the bushing photo. Do not add factory strong. Do not add bounce rate will drop. Do not add already reserved. Verified does not fill the first screen. The original already writes I need OD ID length and tolerance. If the assembly board writes “detail upgrade in progress,” the board is inward. Night shift will reply already new from the board. The board writes first screen pending. The gate gets its own line.

A new salesperson taking over first reads whether this thread has a first-screen original and whether anyone already replied factory strong. No frame: they may only say we are facing the detail first screen. Monday, if last week already locked factory strength outward, write a take-back on this thread first, then look at whether the first screen is still empty. No take-back and they hold two scripts. Edinburgh’s still-one swap, Zurich’s name-and-address fill, Birmingham’s storefront block are not Turin’s spec lift. Neighbour green, this shop a gate: say the two apart.

Turin purchasing already wrote “a bushing with a readable tolerance” into next week’s assembly. Assembly is their calendar. You do not fill it. Reply first-screen status and let them change assembly to detail pending. If an inspection house sent a material sheet with the carton, the sheet can stay. The sheet is not the first screen. Do not change HS to face a detail. Classification is another matter. A group forward of “twenty-screen detail must convert” comes from an outside post. A post is not product preview. Finance wants to book a “detail design fee” on this ticket. A design subject can open. Outward you still have to see the first screen. Design opened and night shift will say studio on so detail done. An advisor is not a detail desk.

Night shift writes “information 4.8 so the detail is fine” onto the roster. Cross that out first. Information score only proves field score. The bushing floor booked the next sinter on your reply. The sinter day is their calendar. Product review walks pass or not. Here edit opens. A gate treats as not facing this SKU. Complaint-takedown walks a takedown. Here nobody complained. There is nothing to take down. No-exposure walks three cells. They already opened the detail. Those three cells are not this week’s steps. The review meeting does not project the welcome line. It projects product-preview first screen and the sentence that took factory strong back. Welcome line hot, first screen still false.

This ticket still hangs HK invoice OK. Letterhead can walk the payment page. The payment page does not write letterhead as the first screen already facing this SKU. The last reply to Turin writes only words that face the page: what the first screen is, whether 20×14×20 is readable. A slogan does not face a page. The store lead pins these sentences on this thread. Night shift may only repeat them. If the clip still holds factory strong next week, cross it out before the shift. Leave it and the old sentence flies again. How showcase quota is lined up already lives on another page. This ticket does not rewrite twenty tiles. Long image facing, right-hand attribute cell still the wrong material: change the cell that faces this SKU.

Questions teams actually ask

Related reading

• First still identifies the SKU
• Which storefront block first
• RFQ first screen walks apart
• Which showcases to fill
• Contact Corpable · info@aliad.hk

Written by Corpable Marketing Limited for Alibaba.com Hong Kong-channel sellers. Not legal, tax, or audit advice. Platform, customs, bank, and auditor outcomes follow the latest official notices. Membership fees go to ALIBABA.COM HONG KONG LIMITED. Corpable does not collect them.